Classification: Public > -----Original Message----- > From: bounce-42904377-109411552@xxxxxxxxxxxxxx [mailto:bounce-42904377- > 109411552@xxxxxxxxxxxxxx] On Behalf Of Eric Covener > Sent: 08 October 2015 13:23 > To: users@xxxxxxxxxxxxxxxx > Cc: mod-auth-cas-dev@xxxxxxxxxxxxxx > Subject: Re:[mod-auth-cas-dev] mod_auth_cas confused by > POST body split across brigades in input filter. > > On Thu, Oct 8, 2015 at 7:34 AM, Mark Blackman <mark.blackman@xxxxxx> > wrote: > > I'd have expected a single call with 476 bytes, can anyone give me > some clues why the filter is called twice for a single request? Is > mod_auth_cas meant to assume the input filter can be called more than > once per request? > > > I have seen it recently somewhere else, in CGI context where the CGI > was not looping over stdin. > > I don't recall the exact cause, but it's something like another module > peeking to see if data is ready ion the connection. The 1 byte it > reads is consumed and set aside, but weaved back in to the next real > read. It's fair to say any input filter has to be prepared to be > called multiple times. Thanks for confirming. So that implies the mod_auth_cas filter code is making an inappropriate and rather fundamental assumption for my case. I suspect that mod_ssl is the module that is peeking into the input stream and triggering a break-up of the inbound request. Cheers, Mark --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures and to http://www.db.com/unitedkingdom/content/privacy.htm for information about privacy. --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|