Aaron,
You may want to try starting the server with option -vv which will
produce a trace on the HTTP server (I think you have to end it to get
the trace written out).
Matt
-----Original Message-----
From: web400-bounces@xxxxxxxxxxxx [mailto:web400-bounces@xxxxxxxxxxxx]
On Behalf Of albartell
Sent: Thursday, September 06, 2007 3:03 PM
To: 'Web Enabling the AS400 / iSeries'
Subject: [WEB400] C#.Net to Apache - empty HTTP POST
Hi all,
Have an interesting one that is stumping me.
I am trying to get a simple C#.Net application to do an HTTP POST to an
Apache instance on an i5, but when I read from standard input in my RPG
there is no data. We know the RPG program is being invoked because we
started a service job and set a breakpoint, it's just the data that
isn't
making it there.
Let me lay out a couple facts:
1) dotNet_PC1 does HTTP POST to i5_V5R4 (intranet) and the post content
is
blank when I try to read it with qtmhrdstin.
2) dotNet_PC1 does HTTP POST to i5_V5R3 (internet) and the post content
comes through fine.
3) java_PC1 does HTTP POST to i5_V5R4 (intranet) and the post content
comes
through just fine.
Basically we have a Windows server with Biztalk on it and the dotNet
code
can't post content to the i5 with V5R4 which is on the same LAN, but a
Java
app on the same Windows Biztalk server _can_ send the post through
successfully. So then we thought we would try to see if a different i5
(which is on V5R3) could receive the post content from the Windows
Biztalk
server and it was _successful_! Both the V5R4 and V5R3 machines have
the
same Apache setup except url and library mappings.
So from there we downloaded WireShark and were peeking at packets going
across the wire. The dotNet app is definitely sending the post content
out,
but for some reason it isn't making it to the i5_V5R4 machine. Note
that
when we execute the dotNet vs. Java that the communication does look
slightly different.
I am curious to know if it is the "Expect: 100-Continue" in the .NET one
that is causing the problem? In the .NET one Apache DOES respond with
an
"HTTP/1.1 100", and _then_ the dotNET sends the POST content. In my
mind I
shouldn't have to worry about this as Apache should be taking care of
the
communication and deliver the POST content as soon as I request it via
qtmhrdstin.
I read about some fixes IBM had to do to Apache because of scripting
attacks
with "Expect:" headers, but I don't believe that would apply in this
case.
Here is what I am talking about:
http://www-1.ibm.com/support/docview.wss?uid=swg1PK24631
Anybody have ideas?
<snip>
Aaron Bartell
http://mowyourlawn.com
midrange.com
