Hi list.

I'm experience a problem with pound and apache httpd server.
May be you know that apache will try to fix automatically
all trailing slash problems e.g:
if I have docroot/test/ folder and someone request http://url/test
apache will respond with 301 Moved Permanently and redirect to 
http://url/test/
but if we use non standard port (not 80 for http or 443 for https)
the request will be: http://url:port/test and apache will redirect to:
http://url:port/test/.
Everything is ok, but let's add and pound to the schema.

I have pound that listen on port 80 and 443 and I have backend
that use non-standard port - 8080 on my test servers

So when a client request http:/url/test - pound connects to port 8080 of 
the backend
and apache web servers respond with something like :  
http://url:8080/test --> 301 Moved Permanently
where the new URL is http://url:8080/test/
pound itself reply to the client with this redirect, but of course port 
8080 is not open on the
server that host pound.

So in brief when someone request http://mysite.com/test - he receive 
redirect to http://mysite.com:8080/test/
but if he try http://mysite.com/test/ it will work.

Is this normal behavior for the balancer and is there any way to fix 
this issue in pound.cfg ?

I found temporary solution using mod_rewrite on the apache but it 
doesn't respect HTTPS request (as it sees only HTTP)

-- 

Best Wishes,
Stefan Lambrev
ICQ# 24134177

Stefan Lambrev wrote:
> Hi list.
> 
> I'm experience a problem with pound and apache httpd server.
> May be you know that apache will try to fix automatically
> all trailing slash problems e.g:
> if I have docroot/test/ folder and someone request http://url/test
> apache will respond with 301 Moved Permanently and redirect to 
> http://url/test/
> but if we use non standard port (not 80 for http or 443 for https)
> the request will be: http://url:port/test and apache will redirect to:
> http://url:port/test/.
> Everything is ok, but let's add and pound to the schema.
> 
> I have pound that listen on port 80 and 443 and I have backend
> that use non-standard port - 8080 on my test servers
> 
> So when a client request http:/url/test - pound connects to port 8080 of 
> the backend
> and apache web servers respond with something like :  
> http://url:8080/test --> 301 Moved Permanently
> where the new URL is http://url:8080/test/
> pound itself reply to the client with this redirect, but of course port 
> 8080 is not open on the
> server that host pound.
> 
> So in brief when someone request http://mysite.com/test - he receive 
> redirect to http://mysite.com:8080/test/
> but if he try http://mysite.com/test/ it will work.
> 
> Is this normal behavior for the balancer and is there any way to fix 
> this issue in pound.cfg ?
> 
> I found temporary solution using mod_rewrite on the apache but it 
> doesn't respect HTTPS request (as it sees only HTTP)
> 

I don't seem to have this problem. Most likely the problem lies with 
your httpd configuration, take a look at this configuration directive:

http://httpd.apache.org/docs/2.2/mod/core.html#usecanonicalname

Hi,

RedShift wrote:
> Stefan Lambrev wrote:
>> Hi list.
>>
>> I'm experience a problem with pound and apache httpd server.
>> May be you know that apache will try to fix automatically
>> all trailing slash problems e.g:
>> if I have docroot/test/ folder and someone request http://url/test
>> apache will respond with 301 Moved Permanently and redirect to 
>> http://url/test/
>> but if we use non standard port (not 80 for http or 443 for https)
>> the request will be: http://url:port/test and apache will redirect to:
>> http://url:port/test/.
>> Everything is ok, but let's add and pound to the schema.
>>
>> I have pound that listen on port 80 and 443 and I have backend
>> that use non-standard port - 8080 on my test servers
>>
>> So when a client request http:/url/test - pound connects to port 8080 
>> of the backend
>> and apache web servers respond with something like :  
>> http://url:8080/test --> 301 Moved Permanently
>> where the new URL is http://url:8080/test/
>> pound itself reply to the client with this redirect, but of course 
>> port 8080 is not open on the
>> server that host pound.
>>
>> So in brief when someone request http://mysite.com/test - he receive 
>> redirect to http://mysite.com:8080/test/
>> but if he try http://mysite.com/test/ it will work.
>>
>> Is this normal behavior for the balancer and is there any way to fix 
>> this issue in pound.cfg ?
>>
>> I found temporary solution using mod_rewrite on the apache but it 
>> doesn't respect HTTPS request (as it sees only HTTP)
>>
>
> I don't seem to have this problem. Most likely the problem lies with 
> your httpd configuration, take a look at this configuration directive:
>
> http://httpd.apache.org/docs/2.2/mod/core.html#usecanonicalname
I'm using apache 1.3 and I have
UseCanonicalName off

Also if I have UseCanonicalName on it will broke a lot of things not 
just folders without trailing slash at the end.

Also do you have apache that listen on port different then 80 ?
>
>

-- 

Best Wishes,
Stefan Lambrev
ICQ# 24134177

On Wed, 2007-05-23 at 13:33 +0300, Stefan Lambrev wrote:
> Hi list.
> 
> I'm experience a problem with pound and apache httpd server.
> May be you know that apache will try to fix automatically
> all trailing slash problems e.g:
> if I have docroot/test/ folder and someone request http://url/test
> apache will respond with 301 Moved Permanently and redirect to 
> http://url/test/
> but if we use non standard port (not 80 for http or 443 for https)
> the request will be: http://url:port/test and apache will redirect to:
> http://url:port/test/.
> Everything is ok, but let's add and pound to the schema.
> 
> I have pound that listen on port 80 and 443 and I have backend
> that use non-standard port - 8080 on my test servers
> 
> So when a client request http:/url/test - pound connects to port 8080 of 
> the backend
> and apache web servers respond with something like :  
> http://url:8080/test --> 301 Moved Permanently
> where the new URL is http://url:8080/test/
> pound itself reply to the client with this redirect, but of course port 
> 8080 is not open on the
> server that host pound.
> 
> So in brief when someone request http://mysite.com/test - he receive 
> redirect to http://mysite.com:8080/test/
> but if he try http://mysite.com/test/ it will work.
> 
> Is this normal behavior for the balancer and is there any way to fix 
> this issue in pound.cfg ?
> 
> I found temporary solution using mod_rewrite on the apache but it 
> doesn't respect HTTPS request (as it sees only HTTP)

Normally this is handled by the RewriteLocation directive - make sure it
is not set to 0. Also check that the redirect is indeed to the back-end
(or to a host that resolves to the same address).
-- 
Robert Segall
Apsis GmbH
Postfach, Uetikon am See, CH-8707
Tel: +41-44-920 4904

Hello!

i had the same problem. can you try if it works with the ip-address from the
pound in the url?
like http://ip-address/test without trailing slash? i think this will work.

in my situation i had to put the dns name into the /etc/hosts configuration
so that pound dont need an trailing slash.
i found this information somewhere in the mailing list archive.

e.g. /etc/hosts:

127.0.0.1 foobar(hostname) foobar.my.company.com(fqhn) myinternetsite.com(fqdn)
-> last one ist also used in the virtual hosts configuration from the
apache.

cu



2007/5/23, Stefan Lambrev <stefan.lambrev(at)sun-fish.com>:
>
> Hi list.
>
> I'm experience a problem with pound and apache httpd server.
> May be you know that apache will try to fix automatically
> all trailing slash problems e.g:
> if I have docroot/test/ folder and someone request http://url/test
> apache will respond with 301 Moved Permanently and redirect to
> http://url/test/
> but if we use non standard port (not 80 for http or 443 for https)
> the request will be: http://url:port/test and apache will redirect to:
> http://url:port/test/.
> Everything is ok, but let's add and pound to the schema.
>
> I have pound that listen on port 80 and 443 and I have backend
> that use non-standard port - 8080 on my test servers
>
> So when a client request http:/url/test - pound connects to port 8080 of
> the backend
> and apache web servers respond with something like :
> http://url:8080/test --> 301 Moved Permanently
> where the new URL is http://url:8080/test/
> pound itself reply to the client with this redirect, but of course port
> 8080 is not open on the
> server that host pound.
>
> So in brief when someone request http://mysite.com/test - he receive
> redirect to http://mysite.com:8080/test/
> but if he try http://mysite.com/test/ it will work.
>
> Is this normal behavior for the balancer and is there any way to fix
> this issue in pound.cfg ?
>
> I found temporary solution using mod_rewrite on the apache but it
> doesn't respect HTTPS request (as it sees only HTTP)
>
> --
>
> Best Wishes,
> Stefan Lambrev
> ICQ# 24134177
>
>
> --
> To unsubscribe send an email with subject 'unsubscribe' to pound(at)apsis.ch.
> Please contact roseg(at)apsis.ch for questions.
> http://www.apsis.ch/pound/pound_list/archive/2007/2007-05/1179916424000
>

Robert Segall wrote:
> On Wed, 2007-05-23 at 13:33 +0300, Stefan Lambrev wrote:
>   
>> Hi list.
>>
>> I'm experience a problem with pound and apache httpd server.
>> May be you know that apache will try to fix automatically
>> all trailing slash problems e.g:
>> if I have docroot/test/ folder and someone request http://url/test
>> apache will respond with 301 Moved Permanently and redirect to 
>> http://url/test/
>> but if we use non standard port (not 80 for http or 443 for https)
>> the request will be: http://url:port/test and apache will redirect to:
>> http://url:port/test/.
>> Everything is ok, but let's add and pound to the schema.
>>
>> I have pound that listen on port 80 and 443 and I have backend
>> that use non-standard port - 8080 on my test servers
>>
>> So when a client request http:/url/test - pound connects to port 8080 of 
>> the backend
>> and apache web servers respond with something like :  
>> http://url:8080/test --> 301 Moved Permanently
>> where the new URL is http://url:8080/test/
>> pound itself reply to the client with this redirect, but of course port 
>> 8080 is not open on the
>> server that host pound.
>>
>> So in brief when someone request http://mysite.com/test - he receive 
>> redirect to http://mysite.com:8080/test/
>> but if he try http://mysite.com/test/ it will work.
>>
>> Is this normal behavior for the balancer and is there any way to fix 
>> this issue in pound.cfg ?
>>
>> I found temporary solution using mod_rewrite on the apache but it 
>> doesn't respect HTTPS request (as it sees only HTTP)
>>     
>
> Normally this is handled by the RewriteLocation directive - make sure it
> is not set to 0. Also check that the redirect is indeed to the back-end
> (or to a host that resolves to the same address).
>   
I think I found what's the problem as I have situation where the problem 
does not exist.
Once I'm 100% sure at which situation pound can't handle the request and 
at which can, I'll send
another mail.