/ Zope / Apsis / Pound Mailing List / Archive / 2007 / 2007-10 / About 303 rewrite?

[ << ] [ >> ]

[ Logging SSL handshake problems / Pär Tögenmark ... ] [ pound log files to use with webalizer? / Matthias ... ]

About 303 rewrite?
Pierre-Alain RIVIERE <pariviere(at)ippon.fr>
2007-10-11 18:39:58 [ FULL ]
Hello,

I'm using Pound as a reverse ssl proxy for an Apache backend which 
serves a Trac (http://trac.edgewall.org/) instance.
Reverse proxy 
function works well but there's something wrong after validating Trac's 
forms.

Indeed, after each form validation, Trac sends a 303 HTTP code to 
redirect the client and Pound seems to not rewrite it correctly.

In my case I want : https://server/<URI>
and after form validation, I got a 303 code to http://server/ (no https 
here). Pound is not configured for dealing with http URL so no response 
at all.

Other location headers, or whatever, are well rewritten. Is it a normal 
behavior of Pound?
As a workaround I can, of course, put Pound listening also on port 80 
and processing a redirection http->https but I'd preferred a better 
solution.

Thanks for help.


Informations
--------------------------------
# dpkg -l | grep pound
ii  pound                            2.2.7-2

# cat /etc/issue
Debian GNU/Linux 4.0




Headers
--------------------------------
https://server/<URI>
 
POST <uri> HTTP/1.1
Host: server
....
Content-Type: application/x-www-form-urlencoded
HTTP/1.x 303 See Other

Location: http://server/<anotheruri>
 



pound.cfg
----------------------------------
ListenHTTPS
        Address hermes
        Port    443
        Cert    "/etc/pound/pound.pem"

        ## allow PUT and DELETE also (by default only GET, POST and HEAD)?:
        xHTTP           2
 

        Service
                HeadRequire "Host: .*server.*"
                BackEnd
                        Address dev
                        Port    80
                End
        End
End

MailBoxer