Hey folks, We're testing a change from apache 2.0.53 to 2.0.55 and we're seeing some weirdness in 2.0.55. In particular, in some cases (note, only a handful, not all of them), the POST data passed through the proxy is... changed. Specifically, it doesn't appear to be URL encoded in key=value paires. For example, here are two snippets of packets, a good and a bad: This is the good one, and there's the key=value that you'd expect: 0x0030 0aa7 f827 6f70 7469 6361 6c5f 7465 7874 ...'optical_text 0x0040 3d77 696c 6c26 763d 314b 4245 4433 6447 =will&v=1KBED3dG 0x0050 7549 4a77 3256 5257 4a58 7733 726b 5754 uIJw2VRWJXw3rkWT 0x0060 4e36 6770 7a59 4255 3067 7049 4b46 7a49 N6gpzYBU0gpIKFzI However, in the bad one you'll notice that you don't see this: 0x0030 0aa8 0f54 504f 5354 202f 6368 6563 6b6f ...TPOST./checko 0x0040 7574 2f72 6573 6572 7665 2f75 6b45 7068 ut/reserve/ukEph ... 0x0420 7465 6e74 2d4c 656e 6774 683a 2035 3138 tent-Length:.518 0x0430 330d 0a0d 0a61 3472 366c 5478 4c35 6971 3....a4r6lTxL5iq 0x0440 7456 556e 4238 366e 7077 376e 6e38 6933 tVUnB86npw7nn8i3 0x0450 704f 6938 7433 5330 574e 6939 3369 416e pOi8t3S0WNi93iAn 0x0460 4c55 6667 3435 4939 5044 5575 4667 446c LUfg45I9PDUuFgDl After "content-length", I'd expect to see "v=a4..." By putting the 2.0.53 mod_proxy_http module into apache 2.0.55, this goes away. Now - in the interest of full disclosure, I'll note that we do have a few small patches in that module which we're combing through to make sure didn't cause this (they're the same as what we applied to 2.0.53), but I wanted to ask here and see if someone said "oh yeah, we changed X for reason Y, you need to do Z" so that we don't chase our tail pointlessly. ;) Thanks. -- Phil Dibowitz P: 310-360-2330 C: 213-923-5115 Unix Admin, Ticketmaster.com
Attachment:
signature.asc
Description: OpenPGP digital signature
|