Unicasting is ok, but risky - I often lose lots of unicasts to spam, and
then there's no list to back me up :)
Also, then other folks in the future don't get their answers...
r->parsed_uri->scheme
http://ci.apache.org/projects/httpd/trunk/doxygen/structrequest__rec.html
Issac
On 08/03/2013 21:16, Nce Rt wrote:
I am unicasting because I didn't hear from others for multiple postings.
feels like spamming the list.
I am still trying to figure out how to get the Scheme (like http,
https,..) info from the incoming request in a custom handler function.
------------------------------------------------------------------------
*From:* Issac Goldstand <mar...@beamartyr.net>
*To:* modules-dev@httpd.apache.org
*Sent:* Thursday, March 7, 2013 12:09 AM
*Subject:* Re: some key fields of request_rec are null
On 06/03/2013 23:21, Nce Rt wrote:
>
>
> A custom handler which is registered to run APR_HOOK_FIRST has these
fields null when processing http request:
> r->content_type, r->parsed_uri.scheme
>
> the http request on the wire has the content_type header set.
>
> r->parsed_uri.path is not null though.
>
>
> apache is configured as reverse proxy here.
>
Hi Nce
1) You didn't say what handler - I assume you mean the default response
handler
2) Although request_rec might be misleading these days with many
server-side frameworks distinguishing between "Response" and "Request"
objects, it doesn't quite work that way in Apache; the request_rec has
worked pretty much the way it does for a loooooooong time. So
r->content_type is actually used to set the *response* content type.
You might want to get Content-Type from r->headers_in
All the best,
Issac
