StreamSend update, now my code doesn't work, 422 Data can't be blank

[jumbojs]

I was using the upload controller with .net. It's been working for at least a couple years now. StreamSend updated to rails 3, now I receive a 422 error, "Data can't be blank".

Anybody else have this issue or know of a solution. I've tried changing variables but nothing is working.

[Chris O'Meara]

Hello,

Thank you for letting me know about your problem with uploads. I have heard similar stories over the past few days and am trying to track down the root cause.

Can you help by providing more details about the request your application sends? The best information would be a capture of the HTTP interaction, without credentials of course. Next best would be a snippet showing how you construct the request in .NET.

Thanks,

Chris O'Meara

On Monday, September 9, 2013, jumbojs wrote:

I was using the upload controller with .net. It's been working for at least a couple years now. StreamSend updated to rails 3, now I receive a 422 error, "Data can't be blank".

Anybody else have this issue or know of a solution. I've tried changing variables but nothing is working.

--
 
---
You received this message because you are subscribed to the Google Groups "StreamSend API Discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to streamsend-api-di...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[John Strzempa]

I have been sending code to Mark A.

--
John Strzempa

[Chris O'Meara]

Ok thank you. I will coordinate with Mark.

[Shannon Massman]

I've just implemented uploads for the first time, and I am also getting this error.

Did you ever find a resolution?

My network capture seems to show my request looks as recommended.

Expect: 100-continue

HTTP/1.1 100 Continue

--e516bc4c-0557-4d48-bf21-f25f7f7ec103
Content-Type: text/plain; charset=utf-8
Content-Disposition: form-data; name=data

... non-encoded ASCII file data ...

--e516bc4c-0557-4d48-bf21-f25f7f7ec103--
HTTP/1.1 422 Unprocessable Entity
Date: Sat, 07 Dec 2013 04:11:13 GMT
Server: Apache
Cache-Control: no-cache
X-Request-Id: ddd13204902e762ccb682c0a4f31b00a
X-UA-Compatible: IE=Edge,chrome=1
X-Rack-Cache: invalidate, pass
Set-Cookie: _session_id=eca6010b2445aa0306c2ebe21620f6c5; path=/; HttpOnly
Status: 422 Unprocessable Entity
Vary: Accept-Encoding
Connection: close
Transfer-Encoding: chunked
Content-Type: application/xml; charset=utf-8

5e

<?xml version="1.0" encoding="UTF-8"?>
<errors>
<error>datacan't be blank</error>
</errors>

0

[Chris O'Meara]

HI Shannon,

The problem mentioned earlier on this thread had to do with a tiny formatting problem in John's request. A previous version of our app server software parsed the request but an upgrade caught the problem. We worked with John to replicate and address the issue.

If you'd like to submit a support ticket we can help you track down the problem.

Cheers,

Chris

--