Shared SSL - The Basics

KaiVar

KaiVar

Guppy
Hi,

I have a shared account on Win2, and am now in a position where I'd like to begin making use of the shared SSL option.

I'd like to apply SSL to some of the subfolders on one of my websites, without affecting any of the other folders and websites, is this possible with shared SSL?

I would be grateful for any information you could provide me for setting this up.

Regards,


Kaine
 
The SSL works more on a subdomain than a sub-folder, so if the subdomain is fine then you will be able to use the Shared SSL as you are testing.
 
Stephen,

Thanks for the response. However, could you let me have a little more detail about how I would use this practically?

Thanks,


Kaine
 
Well it all depends on what you are wanting to do. However I can tell you that ssl in general will not just "work" on a sub folder, as a primary difference between SSL and non SSL site is the address, a website without ssl uses http://domain.com and port 80, a SSL enabled site uses httpS://domain.com and port 443, so you have to design/program around sessions not carrying from non secure to secure (or don't use a standard session, use a cookie, or many other methods).

I am not personally much of a webdesigner, there are many customers here using Shared SSL that maybe be able to help you better than I, I ust gave you a broad overview of it.

If you use Shared ssl you will have an additional sub domain, it will be named https://youruser.myh****re.biz
 
i've installed it on some of my sites, works fine.
as Stephen said - you will have to redirect people to: httpS://yourSiteName.m****here.biz/securePage.asp (ie, you will be redirecting to m-y-h-s-h-p-e-r-e site, but your section on it.

in terms of site structute - again, not an issue, just redirect or link to the above URL.

i often do a check:
if my page would have been at www.site.com/securePage.asp
, on that page, i do an ASP check:
if lcase(request.ServerVariables("HTTPS")) = "off" then response.redirect("https://site.myh-phere.biz/securePage/asp")

works like a charm
 
Hi,

Thanks for the advice. I have had a little experience with SSL on IIS, but that way seems to be a little different to the way that this shared SSL works. In my experience, which is very limited, I could simply apply the security to particular folders. However, with shared SSL, I think I need to set up a subdomain. Now how that is all supposed to work, I'm not exactly sure.

Say I had a folder structure like this:
Code: 
	mysite.com
	       |
		-- NormalFolder
	       |
		-- SecureFolder
My assumptions, and please correct me if I'm wrong, would be to create a subdomain say (admin.mysite.com) on one of my websites, say (mysite.com). Then I make sure that the subdomain has a fixed IP, is this correct so far? Then, since both the domain and subdomain point to the same folder structure, I would simply make the subdomain operate within the shared SSL somehow, is that correct? Then, rather than redirecting to a folder that is secure (remembering to change the protocol from http to https of course), I would simply redirect to the desired folder using the subdomain, thus:


Is this how it is supposed to work?


Kaine
 
no, using the shared SSL of Jodo, you have to use it via THEIR domain. so your site will be the subdomain of jodo. see my example above
(i had to add the dashed into the ".biz" site because this forum automatically puts the stars in, instead of my(-)hsphere.biz)
 
Right then, all that remains is to set the damn thing up. Any idea where I can find a resource that can help me? BTW, does the domain (mysite.com) need to be fixed IP?

Kaine
I feel like I'm inching closer and closer...
 
You must log in or register to reply here.
Back
Top