Sid,
We have had people reporting similar problems in the past and (if my
memory does not fail me) they all ended up being problems on the server
side. What kind of server are you targeting? What kind of library is
being used on the server side to parse multipart form content? 

Another thing you may want to try out is falling back onto HTTP/1.0.
That will automatically disable chunk-encoding, expect-continue
handshake and other features many less widely used HTTP servers usually
have issues with.

Oleg


On Mon, 2003-12-08 at 17:18, Sid Subr wrote:
> but I do not see a 100 continute handshake when I see
> the trace of the request response from and to the
> webserver when I upload the file from a web page using
> the web servers upload funtionality, this could mean
> that the webserver does not expect the expectcontinue
> header right? I tried to set the use expect header to
> tru and false no use and have overridden the
> filepartsource to not give out the encoding.. even
> that does not work.. I am trying to get the wire logs
> working to see if that might help..but having tough
> time to get it to work..
> 
> --- Ortwin_Glck <[EMAIL PROTECTED]> wrote:
> > 
> > 
> > Sid Subr wrote:
> > 
> > > the webserver receives the file fine if uploaded
> > from
> > > a web page..
> > 
> > Could be:
> > - 100 continue handshake problem
> > - transfer encoding problem
> > 
> > 
> >
> ---------------------------------------------------------------------
> > To unsubscribe, e-mail:
> >
> [EMAIL PROTECTED]
> > For additional commands, e-mail:
> > [EMAIL PROTECTED]
> > 
> 
> 
> __________________________________
> Do you Yahoo!?
> New Yahoo! Photos - easier uploading and sharing.
> http://photos.yahoo.com/
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to