After upgrading a machine from V5R4 to V6R1 some B2B clients are now receiving an HTTP 400 error.
The new version of Apache does not appear to be doing anything different when one looks at the trace but there appears to be something that the client now sees differently.
The client is making a B2B connection using a .Net client and has not changed anything at their end so I'm wondering if there is something wrong with the way .Net talks to Apache 2.2.
At V5R4 the client makes an initial POST without authorization credentials. Apache responds with a 401, the client repeats the POST with credentials and all goes well.
It should be noted that the POST actually contains an Expect 100 header so Apache actually responds to the authenticated request with an 100 Continue header which causes the client to then POST the body of the request.
At V6R1 the client makes an initial POST without authorization credentials. Apache responds with a 401, but the client does not appear to accommodate this and immediately responds by a POST with the body of the request.
Apache is expecting to see a valid HTTP header and throws a 400 error when it sees the xml in the body of the request instead.
It's kind of like it is treating the 401 like a 100 response.
This correspondence is for the named person's use only. It may contain confidential
or legally privileged information, or both. No confidentiality or privilege is waived
or lost by any mistransmission. If you receive this correspondence in error, please
immediately delete it from your system and notify the sender. You must not disclose,
copy or rely on any part of this correspondence if you are not the intended recipient.
Any views expressed in this message are those of the individual sender, except where
the sender expressly, and with authority, states them to be the views of Veda Advantage.
If you need assistance, please contact Veda Advantage on either :-
Australia 1300-762-207 or New Zealand +64 9 367 6200
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2021 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.