Re: V6R1 B2B connection error 400

[Peter Connell <Peter.Connell@xxxxxxxxxxxxxxxxx>]

Turns out that this is known to .Net developers connecting to Apache 2.2 using the HttpWebRequest class.
The solution requires the client to add a statement after instantiating the HttpWebRequest class.

HttpWebRequest req = (HttpWebRequest)WebRequest.Create("https://someserver/foo1";);
req.ServicePoint.Expect100Continue = false;

Peter

-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx] On Behalf Of Jack Kingsley
Sent: Saturday, 2 April 2011 1:02 a.m.
To: Web Enabling the AS400 / iSeries
Subject: Re: [WEB400] V6R1 B2B connection error 400

If you can do it compare your IFS security, look at QTMHHTTP and QTMHHTP1.
Also, look at your apache log files.

On Thu, Mar 31, 2011 at 10:21 PM, Peter Connell <
Peter.Connell@xxxxxxxxxxxxxxxxx> wrote:

> Hi,
> 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.
>
> Anyone seen anything like this?
>
> Cheers, Peter
>
>
>
>
> #####################################################################################
>
> 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
> --
> This is the Web Enabling the AS400 / iSeries (WEB400) mailing list
> To post a message email: WEB400@xxxxxxxxxxxx
> To subscribe, unsubscribe, or change list options,
> visit: http://lists.midrange.com/mailman/listinfo/web400
> or email: WEB400-request@xxxxxxxxxxxx
> Before posting, please take a moment to review the archives
> at http://archive.midrange.com/web400.