New SSL URLs!

[stevel]

I was browsing my OPS panel and discovered that I now have new URLs specified for SSL access, in the form: https://server.powweb.com/~username There's also one with just http if you want to get at your site without your domain name. This will help e-commerce users as one no longer needs to use the funny port.

The downside is that this exposes the webuser name, which I am not particularly thrilled about...

[Nino]

Originally posted by stevel
The downside is that this exposes the webuser name, which I am not particularly thrilled about...

I'm not using SSL at the moment, but I wonder: isn't it possible to hide the url by doing a redirect using the .htaccess file and a sub-domain?
For ex.:
have https://secure.yourdomain.com/
and have it point to: https://yourserver.powweb.com/~yourusername/

I don't know if that would work but it's just a thought. (probably not -- maybe I'll try it later)

I do agree that exposing the username name is a downside.
In addition, to the web site visitor, it would look like they're leaving your website.

[stevel]

No, you can't do the redirect. As soon as someone types https://secure.yourdomain.com/, the user will get an error from the browser saying that the certificates don't match.

[tbonekkt]

Originally posted by stevel
The downside is that this exposes the webuser name, which I am not particularly thrilled about...

How about creating a new webuser just for this purpose? That way, you're not revealing the primary username.

[stevel]

It's not clear to me what that accomplishes, though it's good to keep in mind if one chose a webuser name that doesn't look good in a public URL.

[tbonekkt]

Do additional webusers have full control or can access be limited. I haven't created an additional webuser, so I don't know.

[NMS]

what about a cname? Can this hide the long URL and username?

[tbonekkt]

Originally posted by nmsupplies
what about a cname? Can this hide the long URL and username?

How would that differ from a subdomain?

[NMS]

anyway doesn;t let you create a cname

[tbonekkt]

Originally posted by nmsupplies
anyway doesn;t let you create a cname

I wonder why...did you get any error message?

[NMS]

if i am not mistaken... it was invalid host

the problem is the /~username/ part

[Song]

I tried this idea the moment I learned of this change and it did not work. Powweb made sure that the primary Ftp will be the only one tenable. I think they should explain to us the reason for this change or how we will adapt our e-commerce websites to utilize this change.

I made the changes in my Config.php files (both Catalog and Admin) and when I tried the shopping cart, I noticed that it switched automatically from:

https://www.yourdomain.com/~username

TO

https://www.yourdomain.com/12345


So, If any one clearly understands this change, let them communicate. Thank you.

Song

[stevel]

I think you still have the old port number in one of your config files. It doesn't do that to me.

A CNAME won't work, as all it does is provide an alternative host name - not a URL substitution.

As of right now thats how the SSL link will work; however, PowWeb will soon all clients to start using their own Certs for SSL if they wish to. The full details have not been released since this feature is still in the works of being implymented, but i will keep you posted.

Sorry about the typo, what i meant to say was, "PowWeb will soon ALLOW clients to start using their own Certs for SSL if they wish to. " Again, keep in mind that this is still in the works.

Also, for a little explanation as to why the new SSL looks they way it does... Well basically its set this way so that the authentication will run much faster on the server side, so you should notice a difference when using it this way.

[NMS]

I noticed that is indeed faster then it was previously.

I created a cname which points powweb server to my domain and all I managed to achieve was this:

https://anything.mydomain.com/~username

It pops up security screen for the certificate which is issued in the name of powweb.

Again, no, this will NOT work because fo the fact that you are using our Shared SLL link which is using our own Cert. There is no way around it. Sorry.

[JadedMan]

Thank you, thank you, thank you!!! The one MAJOR problem I was having and you guys fixed it! Regular port 443 access is needed to get through most corporate firewalls. Thank you.