Bug #55941 for mod_perl: Incorrect documentation in Apache2::RequestRec

Thu Mar 25 11:40:53 2010 jose.carlos [...] datapulse.net - Ticket created

Subject:	Incorrect documentation in Apache2::RequestRec
Date:	Thu, 25 Mar 2010 15:40:36 +0000
To:	bug-mod_perl [...] rt.cpan.org
From:	Jose Carlos Pereira <jose.carlos [...] datapulse.net>

Good Afternoon We recently upgraded to Apache2. Our proxy code, stopped working, which frustrated us a bit as the code is exactly the same as in the documentation. http://search.cpan.org/~gozer/mod_perl-2.0.4/docs/api/Apache2/RequestRec.pod#proxyreq After much debugging, we changed $r->proxyreq(1) to $r->proxyreq(2), which solved our problems The documentation refers to valid values for proxyreq as: "0, 1 or none" which apparently is incorrect... Maybe referring to the constants would be more correct...? http://search.cpan.org/~gozer/mod_perl-2.0.4/docs/api/Apache2/Const.pod#:proxy best regards -- José Carlos Pereira

Mon Apr 12 15:26:25 2010 PHRED [...] cpan.org - Correspondence added

You're right. Here's from httpd/include/httpd.h /** * @defgroup ProxyReq Proxy request types * * Possible values of request_rec->proxyreq. A request could be normal, * proxied or reverse proxied. Normally proxied and reverse proxied are * grouped together as just "proxied", but sometimes it's necessary to * tell the difference between the two, such as for authentication. * @{ */ #define PROXYREQ_NONE 0 /**< No proxy */ #define PROXYREQ_PROXY 1 /**< Standard proxy */ #define PROXYREQ_REVERSE 2 /**< Reverse proxy */ #define PROXYREQ_RESPONSE 3 /**< Origin response */

Mon Apr 12 15:26:27 2010 The RT System itself - Status changed from 'new' to 'open'

Tue Oct 19 04:13:40 2010 PHRED [...] cpan.org - Correspondence added

The docs are updated to reflect this as of 2.0.5-dev. Thanks for the spot. http://perl.apache.org/docs/2.0/api/Apache2/Const.html#C__proxy_

Tue Oct 19 04:13:40 2010 PHRED [...] cpan.org - Status changed from 'open' to 'resolved'