|
/
Zope
/
Apsis
/
Pound Mailing List
/
Archive
/
2006
/
2006-10
/
url rewritten badly on freebsd
[
FW: [Pound Mailing List] ListenHTTPS and load ... ]
[
Apache ab - SSL read failed - closing connection ... ]
url rewritten badly on freebsd
Stefan Lambrev <stefan.lambrev(at)sun-fish.com> |
2006-10-04 18:19:31 |
[ SNIP ]
|
Is there any reason this configuration file to not work with pound 2.1.3
and FreeBSD ?
ListenHTTP
Address 0.0.0.0
Port 80
End
Service
BackEnd
Address 192.168.13.4
Port 9080
TimeOut 300
End
End
Alive 4
LogLevel 4
Backend is apache 1.3.XX
but on all browsers that I check my request http://url/ is always
rewritten to http://url:9080/
I tried all possible combinations of :
RewriteLocation 0|1|2
RewriteDestination 0|1
w/o any success. I'll test on linux tomorrow.
Am I missing something ?
--
Best Wishes,
Stefan Lambrev
ICQ# 24134177
|
|
|
Re: [Pound Mailing List] url rewritten badly on freebsd
Robert Segall <roseg(at)apsis.ch> |
2006-10-04 18:35:54 |
[ SNIP ]
|
On Wed, 2006-10-04 at 19:19 +0300, Stefan Lambrev wrote:
> Is there any reason this configuration file to not work with pound 2.1.3
> and FreeBSD ?
>
> ListenHTTP
> Address 0.0.0.0
> Port 80
> End
>
> Service
> BackEnd
> Address 192.168.13.4
> Port 9080
> TimeOut 300
> End
> End
> Alive 4
> LogLevel 4
>
> Backend is apache 1.3.XX
> but on all browsers that I check my request http://url/ is always
> rewritten to http://url:9080/
> I tried all possible combinations of :
> RewriteLocation 0|1|2
> RewriteDestination 0|1
> w/o any success. I'll test on linux tomorrow.
> Am I missing something ?
This is probably a result of your application doing something funny
(such as embedding absolute URLs in the web pages). It's unlikely it has
anything to do with Pound.
In any case you should NEVER use 0.0.0.0 as a listener or a back-end, as
it completely defeats the rewriting mechanism (see the man page for
details as to the conditions for rewriting)!
--
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904
|
|
|
Re: [Pound Mailing List] url rewritten badly on freebsd
Cheffo <stefan.lambrev(at)sun-fish.com> |
2006-10-04 20:31:39 |
[ SNIP ]
|
Robert Segall wrote:
> On Wed, 2006-10-04 at 19:19 +0300, Stefan Lambrev wrote:
>
>> Is there any reason this configuration file to not work with pound 2.1.3
>> and FreeBSD ?
>>
>> ListenHTTP
>> Address 0.0.0.0
>> Port 80
>> End
>>
>> Service
>> BackEnd
>> Address 192.168.13.4
>> Port 9080
>> TimeOut 300
>> End
>> End
>> Alive 4
>> LogLevel 4
>>
>> Backend is apache 1.3.XX
>> but on all browsers that I check my request http://url/ is always
>> rewritten to http://url:9080/
>> I tried all possible combinations of :
>> RewriteLocation 0|1|2
>> RewriteDestination 0|1
>> w/o any success. I'll test on linux tomorrow.
>> Am I missing something ?
>>
>
> This is probably a result of your application doing something funny
> (such as embedding absolute URLs in the web pages). It's unlikely it has
> anything to do with Pound.
>
Yes I'll check this for sure :)
The strange thing is that pound 1.9 work just great with this backend,
and that confused me.
Also I do not have set RewriteSomething in pound 1.9 and it just work.
> In any case you should NEVER use 0.0.0.0 as a listener or a back-end, as
> it completely defeats the rewriting mechanism (see the man page for
> details as to the conditions for rewriting)!
>
I'm using 0.0.0.0 to workaround other problem :)
I can't make pound to work with CARP if I use IP, because when I try to
start
second pound on backup CARP iface, it screams with cannot bind - port
already in use.
But this is carp/pf/bsd related.
|
|
|
Re: [Pound Mailing List] url rewritten badly on freebsd
Stefan Lambrev <stefan.lambrev(at)sun-fish.com> |
2006-10-05 17:10:07 |
[ SNIP ]
|
Hello,
Sorry to reply myself.
Cheffo wrote:
> Robert Segall wrote:
>> On Wed, 2006-10-04 at 19:19 +0300, Stefan Lambrev wrote:
>>
>>> Is there any reason this configuration file to not work with pound
>>> 2.1.3 and FreeBSD ?
>>>
>>> ListenHTTP
>>> Address 0.0.0.0
>>> Port 80
>>> End
>>>
>>> Service
>>> BackEnd
>>> Address 192.168.13.4
>>> Port 9080
>>> TimeOut 300
>>> End
>>> End
>>> Alive 4
>>> LogLevel 4
>>>
>>> Backend is apache 1.3.XX
>>> but on all browsers that I check my request http://url/ is always
>>> rewritten to http://url:9080/
>>> I tried all possible combinations of :
>>> RewriteLocation 0|1|2
>>> RewriteDestination 0|1
>>> w/o any success. I'll test on linux tomorrow.
>>> Am I missing something ?
>>>
>>
>> This is probably a result of your application doing something funny
>> (such as embedding absolute URLs in the web pages). It's unlikely it has
>> anything to do with Pound.
>>
> Yes I'll check this for sure :)
> The strange thing is that pound 1.9 work just great with this backend,
> and that confused me.
> Also I do not have set RewriteSomething in pound 1.9 and it just work.
I found where the problem is and I'm not sure that it is only related to
my application server.
I have this line in my httpd.conf:
RewriteRule ^/$ /blabla/ [R]
and from here comes the problem., because for some reason this is
rewritten to :9090/blabla/
I tested with default apache 1.3 configuration with just adding this
rule and the problems persist.
Is it possible that pound make some checks and if the port is 80 it send
request without port but if different
port is specified ... ?
>> In any case you should NEVER use 0.0.0.0 as a listener or a back-end, as
>> it completely defeats the rewriting mechanism (see the man page for
>> details as to the conditions for rewriting)!
>>
> I'm using 0.0.0.0 to workaround other problem :)
> I can't make pound to work with CARP if I use IP, because when I try
> to start
> second pound on backup CARP iface, it screams with cannot bind - port
> already in use.
> But this is carp/pf/bsd related.
>
--
Best Wishes,
Stefan Lambrev
ICQ# 24134177
|
|
|
|