Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 723
  • Last Modified:

HTTP Request returning 500 error

I'm working on a HTTP file upload client, but I can't seem to get it to work. We have a test program that sends the MyImage.JPG file to the server and it works, the server uploads it and saves it in the right folder. We have another program that will display all post requests that it receives, or at least the body portion.

My client was constantly getting a 500 error, our server says: "Fail: End of stream: Class at 1085834" where the number is the length of the request. I decided to just copy and paste the request body from the test client into fiddler and see if that would work. It doesn't. It's getting the exact same error, which tells me something must be wrong in my header because the body is a copy / paste from the receiving end of the test upload program.

Here's the header

POST http://192.168.0.76/SSP.Upload HTTP/1.0
Host: 192.168.0.76
Content-type: multipart/form-data, boundary=----------032612102926055
Content-Length: <length here>

Open in new window


The rest of the request along with the test upload, show post, and MyImage.JPG are all attached in the zip file. If anyone has any suggestions, that would be great. We can't move away from base64, because the guy that wrote the server doesn't have support for binary, but any other suggestions would be great.
PostRequest.zip
0
Curtis Long
Asked:
Curtis Long
  • 3
  • 2
1 Solution
 
Dave BaldwinFixer of ProblemsCommented:
What server is it?
0
 
Curtis LongAuthor Commented:
It's a custom web server
0
 
Dave BaldwinFixer of ProblemsCommented:
Unless you can find someone who has direct experience with that server, it's going to be hard to help you.  We can't look up anything and we won't know what problems there are with the server.  Seems to me that the only one who could really help you is the guy who wrote the server.
0
 
Curtis LongAuthor Commented:
I was hoping my request was breaking a rule of some kind that would be an easy fix, which it was.

I needed to change this:
Content-type: multipart/form-data, boundary=----------032612102926055

Open in new window


to this:

Content-type: multipart/form-data; boundary=----------032612102926055

Open in new window


Semicolon instead of comma. Which I thought I had tried, but it worked after that
0
 
Curtis LongAuthor Commented:
Just a quick simple fix
0

Featured Post

How to Use the Help Bell

Need to boost the visibility of your question for solutions? Use the Experts Exchange Help Bell to confirm priority levels and contact subject-matter experts for question attention.  Check out this how-to article for more information.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now