Mailing-List: contact modules-dev-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: modules-dev@httpd.apache.org
Received-SPF: pass (athena.apache.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:X-Rocket-MIMEInfo:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type;
  b=Hjjif0dRPfnNzuFhWPg8EQ34U0bAJn+G/9kcgoRHKon+VtGjiTzsTUwcCreVytL6udILDJYh5MvyWm4WHDbpGDH9Jgf9OLSuIdeQ4Mo1DnhZITyBJoxr4DzzKGfEaE1vDQrj2BdSeE1aeTXfDAzlge35Abud56XQ0n7jU3twqcI=;
References: <1362441006.68134.YahooMailNeo@web160305.mail.bf1.yahoo.com>
 <1362451213.32498.YahooMailNeo@web160306.mail.bf1.yahoo.com>
 <1362453190.81878.YahooMailNeo@web160305.mail.bf1.yahoo.com>
 <1362601843.6153.YahooMailNeo@web160301.mail.bf1.yahoo.com>
 <5137A86E.3090803@cord.dk>
 <1362604885.95981.YahooMailNeo@web160303.mail.bf1.yahoo.com>
 <51384B43.3060905@beamartyr.net>
 <1362770183.3937.YahooMailNeo@web160301.mail.bf1.yahoo.com>
 <513C4A37.70004@beamartyr.net>
Message-ID: <1363031249.10194.YahooMailNeo@web160301.mail.bf1.yahoo.com>
Date: Mon, 11 Mar 2013 12:47:29 -0700 (PDT)
From: Nce Rt <nce_rt@yahoo.com>
Reply-To: Nce Rt <nce_rt@yahoo.com>
Subject: Re: some key fields of request_rec are null
To: "modules-dev@httpd.apache.org" <modules-dev@httpd.apache.org>
In-Reply-To: <513C4A37.70004@beamartyr.net>
MIME-Version: 1.0
Content-Type: multipart/alternative;
 boundary="1332810471-1250720809-1363031249=:10194"

--1332810471-1250720809-1363031249=:10194
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: quoted-printable

that's what is null I've been talking about past 2 weeks!!=0A=0A=0A________=
________________________=0A From: Issac Goldstand <margol@beamartyr.net>=0A=
To: Nce Rt <nce_rt@yahoo.com> =0ACc: modules-dev@httpd.apache.org =0ASent: =
Sunday, March 10, 2013 12:54 AM=0ASubject: Re: some key fields of request_r=
ec are null=0A =0AUnicasting is ok, but risky - I often lose lots of unicas=
ts to spam, and =0Athen there's no list to back me up :)=0A=0AAlso, then ot=
her folks in the future don't get their answers...=0A=0Ar->parsed_uri->sche=
me=0A=0Ahttp://ci.apache.org/projects/httpd/trunk/doxygen/structrequest__re=
c.html=0A=0A=A0  Issac=0A=0AOn 08/03/2013 21:16, Nce Rt wrote:=0A> I am uni=
casting because I didn't hear from others for multiple postings.=0A> feels =
like spamming the list.=0A>=0A> I am still trying to figure out how to get =
the Scheme (like http,=0A> https,..) info from the incoming request in a cu=
stom handler function.=0A>=0A> --------------------------------------------=
----------------------------=0A> *From:* Issac Goldstand <margol@beamartyr.=
net>=0A> *To:* modules-dev@httpd.apache.org=0A> *Sent:* Thursday, March 7, =
2013 12:09 AM=0A> *Subject:* Re: some key fields of request_rec are null=0A=
>=0A> On 06/03/2013 23:21, Nce Rt wrote:=0A>=A0 >=0A>=A0 >=0A>=A0 > A custo=
m handler which is registered to run APR_HOOK_FIRST has these=0A> fields nu=
ll when processing http request:=0A>=A0 >=A0 =A0 =A0 r->content_type, r->pa=
rsed_uri.scheme=0A>=A0 >=0A>=A0 > the http request on the wire has the cont=
ent_type header set.=0A>=A0 >=0A>=A0 > r->parsed_uri.path is not null thoug=
h.=0A>=A0 >=0A>=A0 >=0A>=A0 > apache is configured as reverse proxy here.=
=0A>=A0 >=0A>=0A> Hi Nce=0A>=0A> 1) You didn't say what handler - I assume =
you mean the default response=0A> handler=0A> 2) Although request_rec might=
 be misleading these days with many=0A> server-side frameworks distinguishi=
ng between "Response" and "Request"=0A> objects, it doesn't quite work that=
 way in Apache; the request_rec has=0A> worked pretty much the way it does =
for a loooooooong time.=A0 So=0A> r->content_type is actually used to set t=
he *response* content type.=0A> You might want to get Content-Type from r->=
headers_in=0A>=0A> All the best,=0A>=A0 =A0 Issac=0A>=0A>
--1332810471-1250720809-1363031249=:10194--