Shared SSL - Page 2

**3pm** · October 18th, 2004, 9:45 PM

I had problems getting to my account through the IP before and it was only because I forgot to put the "/" at the end. Could just be my browser that doesn't like it like that.

I hit my site with the https and it shows up like it is secure, but there is a warning first that says something about it not actually being secure.

**Bigjohn** · September 9th, 2005, 11:36 AM

ok.. now, dumb question.. probably a complete lack of coffee... but how do you USE it? Is there a special thing you do on cpanel? or a special folder to put secure stuff into? OY! my brain hurts from working too much and not sleeping...

**fwwebs5** · September 9th, 2005, 11:59 PM

Nothing special. https://ip_address/~username/ will render the users public_html directory files. Additionally, you can use your domain to access the SSL.
https://yourdomain.tld/
Whether using http or https the DNS will resolve the same IP address. Since the server doesn't have a dedicated secure account, it will render the default page. Once you add the ~username, because of mod_userdir, it will access that users public_html directory files.
https://yourdomain.tld/~yourusername/

The problem with shared ssl is two fold:
1. Unless the secure site is accessed by the correct domain and the certificate is legitimate, (not self-signed as most are) you'll receive a warning.
2. Because the path is derived differently, your pages will need hard coded links.

https://yourdomain.tld/~yourusername/index.html has a relative link

PHP Code:


			
<a href=test.html>test.html</a>

the link created will actually be https://yourdomain.tld/test.html. Image tags will suffer the same issue. The workaround is to use specific pages for shared ssl and code the links appropriately.

PHP Code:


			
<a href=https://yourdomain.tld/~yourusername/test.html>test.html</a>

October 18th, 2004, 9:45 PM	#10 (permalink)
3pm Surpass Fan Seasoned Poster Joined in Jul 2003 53 posts Gave thanks: 0 Thanked 0 times	I had problems getting to my account through the IP before and it was only because I forgot to put the "/" at the end. Could just be my browser that doesn't like it like that. I hit my site with the https and it shows up like it is secure, but there is a warning first that says something about it not actually being secure. __________________ Three Pillars Media - Reseller - phantom dime99 -

September 9th, 2005, 11:36 AM	#11 (permalink)
Bigjohn minor deity Super #1 Joined in Apr 2004 Lives in Georgia Hosted on XEON 7,387 posts Gave thanks: 28 Thanked 94 times	ok.. now, dumb question.. probably a complete lack of coffee... but how do you USE it? Is there a special thing you do on cpanel? or a special folder to put secure stuff into? OY! my brain hurts from working too much and not sleeping... __________________ Proud to be a Surmunity Mod! XEON PASS60 PASS61 Make a fundamental difference! My Sites: Curious about Brewing Beer? Join the community! >>>>> Some Change is GOOD! Keep your paycheck! Support the Fair Tax Get into an Art museum Victorian London It's your brain -*ON WEB* - mybrainhost.com (under development) What SHOULD Government do? Much Less than it Does!

September 9th, 2005, 11:59 PM	#12 (permalink)
fwwebs5 Surpass Fan On a golden path... Joined in Nov 2003 432 posts Gave thanks: 0 Thanked 0 times	Nothing special. https://ip_address/~username/ will render the users public_html directory files. Additionally, you can use your domain to access the SSL. https://yourdomain.tld/ Whether using http or https the DNS will resolve the same IP address. Since the server doesn't have a dedicated secure account, it will render the default page. Once you add the ~username, because of mod_userdir, it will access that users public_html directory files. https://yourdomain.tld/~yourusername/ The problem with shared ssl is two fold: 1. Unless the secure site is accessed by the correct domain and the certificate is legitimate, (not self-signed as most are) you'll receive a warning. 2. Because the path is derived differently, your pages will need hard coded links. https://yourdomain.tld/~yourusername/index.html has a relative link PHP Code: `<a href=test.html>test.html</a>` the link created will actually be https://yourdomain.tld/test.html. Image tags will suffer the same issue. The workaround is to use specific pages for shared ssl and code the links appropriately. PHP Code: `<a href=https://yourdomain.tld/~yourusername/test.html>test.html</a>` __________________ Fw Web Solutions http://fwwebs.com

Thread Tools	Search this Thread
Show Printable Version Email this Page	Search this Thread: Advanced Search
Rate This Thread
Rate This Thread:

Currently Active Users Viewing This Thread: 1 (0 members and 1 guests)