Jump to content

Working with a SSL Proxy


thomas
 Share

Recommended Posts

Hello,

I want to build a facebook tab for my website, but FB requires SSL. So I have an option to use an ssl proxy for my domain which sounds like https://ssl-account.com/domain-name/ ... A quick check reveals my page but of course no links work or images appear since they are all absolutely linked to /.

I can't seem to access any page but home (/) though. Every time I want to access say https://ssl-account.com/domain-name/news/ it redirects to https://ssl-account.com/news which obviously doesn't work.

I only need one single page with one template to work with SSL. Has anyone got any experience with this?

Thanks,

thomas

Link to comment
Share on other sites

Double check that this isn't the result of cache. Go ahead and login at https://ssl-account.com/domain-name/processwire/. Now browse the site. Does it work? If so, check to see if you have any caches enabled and disable them. 

Also, double check that when you link to assets in your site, you are using a variables like $config->urls->root rather than "/"; and $config->urls->templates, rather than "/site/templates/"; etc. 

Link to comment
Share on other sites

Hello Ryan,

I think I found it. Whenever I forget the trailing slah, it redirects. So https://ssl-account.com/neu.bigair.tv/admin/ works (even though no stylesheets or anything is found) but https://ssl-account.com/neu.bigair.tv/admin redirects to https://ssl-account.com/admin which of course doesn't work at all.

I'll try to get this to work with that.

Thanks!

thomas

  • Like 1
Link to comment
Share on other sites

  • 4 years later...

I have the same problem, trying to get a site working with an optional SSL Proxy. The site should work with and without the proxy. I think the problem is that all paths in PW are relative, so they think the SSL Proxy is the root, and all paths miss out the actual domain then. I was experimenting with prepending all URLs in my templates with something like `/my-domain.com` in case a HTTP_X_FORWARDED_HOST is set (that's the proxy). This works well with all public parts of the site (= my templates), but not for the admin parts, which are actually the only reason the proxy would make sense.

I'm looking for a way to 'repair' the admin paths like i did with my other paths for pages and assets, but have no clue how to manipulate them.
Any hints welcome!

Thanks,
AA

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...