[Carlos]

HttpPost is not sending any params passed to it (ie, I want to send "POST /worklist/storename?session=1234&action=getWorkItem HTTP/1.0", but only "POST /worklist HTTP/1.0" is sent). I suppose there's a good logic for it, but I'd like to know of some option that doesn't include changing the server.

[kris]

HTTP POST does not operate in the same manner as a GET, because the former are not supposed to be arbitrarily repeated (think casting a vote, versus checking your mailbox). Arguments for post are passed as part of the request body instead (IIRC), and part of the reason for this is so that one cannot easily bookmark a POST.

You can read up on POST at wc3.org, and I got some solid guidance on POST redirection handling from here: http://ppewww.ph.gla.ac.uk/~flavell/www/post-redirect.html

That link on redirection provides some insight on the mess that HTTP has become

[Carlos]

I was thinking it was something along those lines, but I was still hoping there would be a solution. Looks like I'll have to resort to another solution anyway.