> Call doPost from doGet.
>
[quoted text clipped - 4 lines]
>
> }
In article <1139560490.541849.157290@g44g2000cwa.googlegroups.com>,
schonlinner@yahoo.com took the hamburger, threw it on the grill, and I
said "Oh wow"...
> trippy schrieb:
> > In article <1139493130.464358.47440@z14g2000cwz.googlegroups.com>,
[quoted text clipped - 24 lines]
>
> Nice idea, but does not work:
Yes it does. It's what you're supposed to do when you want a servlet
that handles both post and get requests.
> When we execute the HTTP POST command, we
> transfer some data in the body of the HTTP request. Apparently a HTTP
> GET request cannot transfer that data, thus that data does not arrive
> at the servlet.
Oooh, I get it now. That's a different animal and I'm not sure about
that. Any idea what causes that? Because in theory at least, whatever
that would get transferred to the doPost will be same thing as what the
doGet call would get.
> Our server then has an incomplete GET request which
> originally was a POST request. We don't know why the proxy in-between
> "changed" something and thus destroyed the original HTTP request.
>
> Best regards,
> Alex

Signature
trippy
mhm31x9 Smeeter#29 WSD#30
sTaRShInE_mOOnBeAm aT HoTmAil dOt CoM
NP: "Jellyroll" -- Blue Murder
"Now, technology's getting better all the time and that's fine,
but most of the time all you need is a stick of gum,
a pocketknife, and a smile."
-- Robert Redford "Spy Game"
schonlinner@yahoo.com - 10 Feb 2006 11:09 GMT
> Oooh, I get it now. That's a different animal and I'm not sure about
> that. Any idea what causes that? Because in theory at least, whatever
> that would get transferred to the doPost will be same thing as what the
> doGet call would get.
No, I don't know what is causing that problem and why the proxy is
changing and thus destroying the request. But as nobody has an
explanation for that and keeping in mind that thousands of other people
make very similar things (i.e. create HTTP connections to a servlet
from an applet using URLConnection, etc.) and apparently don't have
such problems it seems to be some kind of other (non-discovered) bug in
my code when creating the request.
Perhaps it's an unknown HTTP header parameter (we use some custom HTTP
header parameters to transport some information). Or perhaps it's
because the HTTP body does not contain name/value pairs, instead it
contains just serialized java objects...I really don't know :-((
Best regards,
Alex