serendipity behind a portal

[michaelgsandtner]

I successfully login to the administrator page, but when clicking any function, the login page is displayed again.
The client browser contacts our enterprise portal (which does authentication, beside many other things), which in turn contacts the serendipity host, which is different from the portal host.
I realized (with help of Firefox LiveHTTPheader extension), that the cookies are set for the serendipity hostname (domain= in the SetCookie http header), which are never sent by the browser because of the different names of portal and serendipity host.
A quick and dirty solution was to replace in all .php files all occurrences of $_SERVER['HTTP_HOST'] with $_SERVER['HTTP_X_ORIG_HOSTINFO']. This header is set by our enterprise portal, and contains the portal host contacted by the client. I assume, several other things should better be changed too.
All this leads to my feature request: make serendipity runnable behind a portal; do not assume, that the client browser directly contacts serendipity (mediawiki e.g. uses a configuration option $wgServerName for that purpose).

Best regards --Michi

[garvinhicking]

Hi!

Yes, s9y is not meant to run in such an environment. There are many plugins and other things where you need to change HTTP_HOST in this case.

Maybe you should simply patch serendipity_config and set $_SERVER['HTTP_HOST'] = $_SERVER['HTTP_X_ORIG_HOSTINFO'].

I have no knowledge of such setups, so we would need a developer who has.

Best regards,
Garvin