Can"t locate object method "STORE" via package"APR::Request::Param::Table"
am 25.02.2011 17:53:29 von James.B.Muir --_000_527C4914F1B2EA47B38422DE0FA05A65064B6C3ED9DH201DHMCMa st_
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Hello,
I am using the excellent Apache2::Request module.
I'm writing a mod_perl2 authen handler. I'd like to be able to modify the v=
alue of, or delete, a parameter and then allow the request to be further pr=
ocessed by the mod_jk response handler.
Based on my reading it looks like it should be easy to handle requests sent=
with the GET method. However, I've also got to be able to handle the POST =
method. Based on my testing of the POST method I see the following error me=
ssage in the apache2 error log:
Can't locate object method "STORE" via package "APR::Request::Param::Table"
My reading suggests to me that it is not possible to modify the value of, o=
r remove, a parameter in the body of a POST request and pass that modified =
body to mod_jk.
Is this true?
-James
IMPORTANT NOTICE REGARDING THIS ELECTRONIC MESSAGE:
This message is intended for the use of the person to whom it is addressed =
and may contain information that is privileged, confidential, and protected=
from disclosure under applicable law. If you are not the intended recipien=
t, your use of this message for any purpose is strictly prohibited. If you =
have received this communication in error, please delete the message and no=
tify the sender so that we may correct our records.
--_000_527C4914F1B2EA47B38422DE0FA05A65064B6C3ED9DH201DHMCMa st_
Content-Type: text/html; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
xmlns:x=3D"urn:schemas-microsoft-com:office:excel" xmlns:p=3D"urn:schemas-m=
icrosoft-com:office:powerpoint" xmlns:a=3D"urn:schemas-microsoft-com:office=
:access" xmlns:dt=3D"uuid:C2F41010-65B3-11d1-A29F-00AA00C14882" xmlns:s=3D"=
uuid:BDC6E3F0-6DA3-11d1-A2A3-00AA00C14882" xmlns:rs=3D"urn:schemas-microsof=
t-com:rowset" xmlns:z=3D"#RowsetSchema" xmlns:b=3D"urn:schemas-microsoft-co=
m:office:publisher" xmlns:ss=3D"urn:schemas-microsoft-com:office:spreadshee=
t" xmlns:c=3D"urn:schemas-microsoft-com:office:component:spread sheet" xmlns=
:odc=3D"urn:schemas-microsoft-com:office:odc" xmlns:oa=3D"urn:schemas-micro=
soft-com:office:activation" xmlns:html=3D"http://www.w3.org/TR/REC-html40" =
xmlns:q=3D"http://schemas.xmlsoap.org/soap/envelope/" xmlns:rtc=3D"http://m=
icrosoft.com/officenet/conferencing" xmlns:D=3D"DAV:" xmlns:Repl=3D"http://=
schemas.microsoft.com/repl/" xmlns:mt=3D"http://schemas.microsoft.com/share=
point/soap/meetings/" xmlns:x2=3D"http://schemas.microsoft.com/office/excel=
/2003/xml" xmlns:ppda=3D"http://www.passport.com/NameSpace.xsd" xmlns:ois=
=3D"http://schemas.microsoft.com/sharepoint/soap/ois/" xmlns:dir=3D"http://=
schemas.microsoft.com/sharepoint/soap/directory/" xmlns:ds=3D"http://www.w3=
..org/2000/09/xmldsig#" xmlns:dsp=3D"http://schemas.microsoft.com/sharepoint=
/dsp" xmlns:udc=3D"http://schemas.microsoft.com/data/udc" xmlns:xsd=3D"http=
://www.w3.org/2001/XMLSchema" xmlns:sub=3D"http://schemas.microsoft.com/sha=
repoint/soap/2002/1/alerts/" xmlns:ec=3D"http://www.w3.org/2001/04/xmlenc#"=
xmlns:sp=3D"http://schemas.microsoft.com/sharepoint/" xmlns:sps=3D"http://=
schemas.microsoft.com/sharepoint/soap/" xmlns:xsi=3D"http://www.w3.org/2001=
/XMLSchema-instance" xmlns:udcs=3D"http://schemas.microsoft.com/data/udc/so=
ap" xmlns:udcxf=3D"http://schemas.microsoft.com/data/udc/xmlfile " xmlns:udc=
p2p=3D"http://schemas.microsoft.com/data/udc/parttopart" xmlns:wf=3D"http:/=
/schemas.microsoft.com/sharepoint/soap/workflow/" xmlns:dsss=3D"http://sche=
mas.microsoft.com/office/2006/digsig-setup" xmlns:dssi=3D"http://schemas.mi=
crosoft.com/office/2006/digsig" xmlns:mdssi=3D"http://schemas.openxmlformat=
s.org/package/2006/digital-signature" xmlns:mver=3D"http://schemas.openxmlf=
ormats.org/markup-compatibility/2006" xmlns:m=3D"http://schemas.microsoft.c=
om/office/2004/12/omml" xmlns:mrels=3D"http://schemas.openxmlformats.org/pa=
ckage/2006/relationships" xmlns:spwp=3D"http://microsoft.com/sharepoint/web=
partpages" xmlns:ex12t=3D"http://schemas.microsoft.com/exchange/service s/20=
06/types" xmlns:ex12m=3D"http://schemas.microsoft.com/exchange/service s/200=
6/messages" xmlns:pptsl=3D"http://schemas.microsoft.com/sharepoint/soap/ Sli=
deLibrary/" xmlns:spsl=3D"http://microsoft.com/webservices/SharePointPor tal=
Server/PublishedLinksService" xmlns:Z=3D"urn:schemas-microsoft-com:" xmlns:=
st=3D"" xmlns=3D"http://www.w3.org/TR/REC-html40">
>
ze:10.0pt;font-family:"Courier New"">Hello,
ze:10.0pt;font-family:"Courier New"">
ze:10.0pt;font-family:"Courier New"">I am using the excellent Apa=
che2::Request module.
ze:10.0pt;font-family:"Courier New"">
ze:10.0pt;font-family:"Courier New"">I’m writing a mod_perl=
2 authen handler. I’d like to be able to modify the value of, or dele=
te, a parameter and then allow the request to be further processed
by the mod_jk response handler.
ze:10.0pt;font-family:"Courier New"">
ze:10.0pt;font-family:"Courier New"">Based on my reading it looks=
like it should be easy to handle requests sent with the GET method. Howeve=
r, I’ve also got to be able to handle the POST method.
Based on my testing of the POST method I see the following error message i=
n the apache2 error log:
ze:10.0pt;font-family:"Courier New"">
ze:10.0pt;font-family:"Courier New"">Can't locate object method &=
quot;STORE" via package "APR::Request::Param::Table”
o:p>
ze:10.0pt;font-family:"Courier New"">
ze:10.0pt;font-family:"Courier New"">My reading suggests to me th=
at it is not possible to modify the value of, or remove, a parameter in the=
body of a POST request and pass that modified body
to mod_jk.
ze:10.0pt;font-family:"Courier New"">
ze:10.0pt;font-family:"Courier New"">Is this true?
ze:10.0pt;font-family:"Courier New"">-James
ze:10.0pt;font-family:"Courier New"">
IMPORTANT NOTICE REGARDIN=
G THIS ELECTRONIC MESSAGE:
This message is intended for the use of the person to whom it is addressed =
and may contain information that is privileged, confidential, and protected=
from disclosure under applicable law. If you are not the intended recipien=
t, your use of this message for
any purpose is strictly prohibited. If you have received this communicatio=
n in error, please delete the message and notify the sender so that we may =
correct our records.
--_000_527C4914F1B2EA47B38422DE0FA05A65064B6C3ED9DH201DHMCMa st_--