Bit OT thos one, but figure a lot of you are using Lighttpd on Textdrive. We have setup lighttpd with all the proxying as recommended in the manual and this is all working well with our rails app. However, we have a php app which is now not leting us login due to cookie issues. We do not have access to the source unfortunately, as it''s Zend encoded. Looking at the headers, it seems to be setting the cookie as so: Set-Cookie: foo=bar; path=/; domain=.domain.co.uk:8102 But the browser never sets the cookie. I''m assuming the problem is with the port being specified, as it thinks we''re on 8102 when in actual fact it''s being accessed over port 80. Although even when I access the site and explicitly set port 8102 it still doesn''t work. Note that this was all working prior to changing over when we were using apache. Anyone come across before and know of any fixes? Either: - get apache instead of Lighttpd being used just for this dir with the php in - get the cookies working with the Lighttpd redirects etc... I posted an urgent support request to TD the other day, but haven''t heard anything at all back from them. Thanks guys. -- R.Livsey http://livsey.org
I had a similar issue with typos rss feeds. Try setting ProxyPreserveHost on ( "Preserve original Host: header" under ''proxying'' in webmins apache config ) and you might need to disable lighttpd keepalives too - see http://number9.hellooperator.net/articles/2005/09/21/zoom-zoom On 30/09/05, Richard Livsey <richard-gfRugNUWsoQdnm+yROfE0A@public.gmane.org> wrote:> Bit OT thos one, but figure a lot of you are using Lighttpd on Textdrive. > > We have setup lighttpd with all the proxying as recommended in the > manual and this is all working well with our rails app. > > However, we have a php app which is now not leting us login due to > cookie issues. > > We do not have access to the source unfortunately, as it''s Zend encoded. > > Looking at the headers, it seems to be setting the cookie as so: > > Set-Cookie: foo=bar; path=/; domain=.domain.co.uk:8102 > > But the browser never sets the cookie. I''m assuming the problem is with > the port being specified, as it thinks we''re on 8102 when in actual fact > it''s being accessed over port 80. > > Although even when I access the site and explicitly set port 8102 it > still doesn''t work. > > Note that this was all working prior to changing over when we were using > apache. > > Anyone come across before and know of any fixes? > > Either: > > - get apache instead of Lighttpd being used just for this dir with the > php in > - get the cookies working with the Lighttpd redirects etc... > > I posted an urgent support request to TD the other day, but haven''t > heard anything at all back from them. > > Thanks guys. > > -- > R.Livsey > http://livsey.org > > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Rasputin :: Jack of All Trades - Master of Nuns
Superb, many thanks. ProxyPreserveHost did the trick. -- R.Livsey http://livsey.org Dick Davies wrote:>I had a similar issue with typos rss feeds. >Try setting > >ProxyPreserveHost on > >( "Preserve original Host: header" under ''proxying'' in webmins apache config ) > >and you might need to disable lighttpd keepalives too - see > >http://number9.hellooperator.net/articles/2005/09/21/zoom-zoom > > >On 30/09/05, Richard Livsey <richard-gfRugNUWsoQdnm+yROfE0A@public.gmane.org> wrote: > > >>Bit OT thos one, but figure a lot of you are using Lighttpd on Textdrive. >> >>We have setup lighttpd with all the proxying as recommended in the >>manual and this is all working well with our rails app. >> >>However, we have a php app which is now not leting us login due to >>cookie issues. >> >>We do not have access to the source unfortunately, as it''s Zend encoded. >> >>Looking at the headers, it seems to be setting the cookie as so: >> >>Set-Cookie: foo=bar; path=/; domain=.domain.co.uk:8102 >> >>But the browser never sets the cookie. I''m assuming the problem is with >>the port being specified, as it thinks we''re on 8102 when in actual fact >>it''s being accessed over port 80. >> >>Although even when I access the site and explicitly set port 8102 it >>still doesn''t work. >> >>Note that this was all working prior to changing over when we were using >>apache. >> >>Anyone come across before and know of any fixes? >> >>Either: >> >>- get apache instead of Lighttpd being used just for this dir with the >>php in >>- get the cookies working with the Lighttpd redirects etc... >> >>I posted an urgent support request to TD the other day, but haven''t >>heard anything at all back from them. >> >>Thanks guys. >> >>-- >>R.Livsey >>http://livsey.org >> >>_______________________________________________ >>Rails mailing list >>Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >>http://lists.rubyonrails.org/mailman/listinfo/rails >> >> >> > > >-- >Rasputin :: Jack of All Trades - Master of Nuns >_______________________________________________ >Rails mailing list >Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org >http://lists.rubyonrails.org/mailman/listinfo/rails > > > > >