Use admin-script with different hostname and Path

[Boris]

I am currently using my Blog on an URL like

Code: Select all

http://example.com

and I would like to admin it via HTTPS, which I can use over a proxy located at my Webhoster. But every time I visit the s9y-admin-script there

Code: Select all

https://webhoster/path/to/s9y/serendipity_admin.php

it redirects me to

Code: Select all

http://example.com/serendipity_admin.php

I tried an set "Dectect HTTP-Hostname automatically", but that did not help. Is there any way to do this?

[garvinhicking]

Use a tool like LiveHTTP Headers to see where/how the redirection takes place.

You cannot use Serendipity on 2 different paths though. Using it on

http://server1/serendpity/
https://server2/

is not possible because of different serendipityHTTPPath settings, which are used quite often.

Regards,
Garvin

[bogus]

I got the same problem after upgrading to s9y-1.4.1.

My blog is hosted via http, let's say http://mydomain.com/blog
and I want to use the admin-interface via a SSL-proxy of my provider using a different Url, f.e. https://ssl.myprovider.com/blog.

With s9y-1.1 it was no problem to use the admin-site via this SSL-proxy, but using s9y-1.4.1 it's not useable anymore... ;/

I enabled "Detect HTTP-Hostname automatically" too.
I can login, but when I click a link at the sidebar, f.e. to create a new blog entry, I get redirected to the login-page again (on the SSL-Proxy).

I use the same path "/blog" directly via mydomain.de and via ssl.myprovider.de:
http://mydomain.com/blog
https://ssl.myprovider.com/blog

I don't know what exactly the problem is... looking at "Live-http-headers" I see that the admin-site is sending "http://mydomain.com/..." as referer ... might that be the problem ?

Is it possible to use the admin-site like this... via a different SSL-Proxy-Url but with the same path ?

Can anyone help me to solve this issue ?

[garvinhicking]

Hi!

Usually, when you get logged out this is a session issue. Have you checked if the PHP session.save_path points to a valid directory and your browser is accepting cookies?

S9y 1.1 did not issue a cookie domain, this needed fixing due to some bugs with that on servers that want to share session cookies through http and https, so s9y 1.4 does use the cookie domain name. So depending on your setup maybe the cookie gets set for a wrong domain. Sadly I have never used SSL proxying, so I'm not familiar with what it does exactly.

Using LiveHTTPHeaders you should be able to see which cookies get send; pay a close eye on the "Cookie: PHPSESSID" header, and if the one that is sent to your client is the same that gets sent back later to the pages where you need to re-login?

Regards,
Garvin