hi,
i have a winforms app sending dime attachments to a WSE 2.0 web
service. it reads a set chunksize of bytes of a file into a memory
stream > into the dime attachment > send to the web service.
the web service then reads the stream and appends the bytes to the
file. it's a large file upload solution.
BUT... when the size of the bytes sent in the dime attachement is
between 48000 and 60000, it fails every time with HTTP status 400 bad
request.
if i go above or below those limits, by a lot or a little, it works
perfectly, every time.
i came across this by chance when i was experimenting the efficiency of
the algorithm with different size of chunks sent each time.
what the?!!
if anyone wants to see the source code i can send them the VS solution.
tim.
p.s. my maxRequestLength in httpruntime (machine.config) is 256000, as
is the microsoft.web.services2 > messaging > maxRequestLength value in
web.config.
[MSFT] - 09 Aug 2005 03:00 GMT
Hello Tim,
It is really a weird problem. Can you post your code here or send me by
email (please remove "online." from my email address). I will test it to
see if I can reproduce it.
Thanks,
Luke
[MSFT] - 09 Aug 2005 11:57 GMT
Hello Tim,
Your code looks perfect and it works well on my server. Have you tested
your code on other computer? It may be server-specified issue, for example,
is there any firewall/proxy on the server?
Luke
Tim_Mac - 09 Aug 2005 17:27 GMT
hi Luke,
thanks for testing it out. i tried it on a production server (win 2003
enterprise) and it worked fine. on my XP Pro box, which is causing the
problems, i tried turning off my anti virus (AVG) and Windows Firewall
on the network connection (although i'm browsing localhost anyway) just
to see if that could unearth anything, but there was no change in
behaviour.
i guess i don't mind as long as it works reliably on IIS 6 which is the
only platform i use for production applications anyway.
it's mighty strange, and hard to pin down because it's an IIS error and
there's nothing i can debug my app about. i have run IIS lockdown on
this box, but that wouldn't be an obvious explanation.
thanks for your help anyway. i'm happy enough to let it go unless
anyone has further ideas for why this might be happening.
tim.
[MSFT] - 10 Aug 2005 03:39 GMT
Hell Tim,
If you need further investment on this issue, I suggest you may perform a
network capture to monitor the data transfer between client and server. You
may begin with this article:
http://support.microsoft.com/default.aspx?scid=KB;EN-US;Q247249
Luke