Extra data in upload response

figbug · January 17, 2012

I've kinda been ignoring my app for quite a while. A user just reported that it's no longer uploading. Looking at the response I get from the server it looks like this:

HTTP/1.1 200 OK
Cache-Control: private, no-store, no-cache, max-age=1, must-revalidate
Content-Type: text/xml; charset=utf-8
Date: Tue, 17 Jan 2012 17:05:22 GMT
Edge-Control: no-store
Expires: Tue, 17 Jan 2012 17:05:23 GMT
Server: Apache
X-Powered-By: SmugMug/0.9
X-SmugMug-Hiring: How to love what you do: http://www.smugmug.com/jobs/
X-SmugMug-Values: 1/4 - Thrill your customers
transfer-encoding: chunked
Connection: keep-alive

27
<?xml version="1.0" encoding="utf-8"?> 
b9

<rsp stat="ok"><method>smugmug.images.upload</method><Image id="1675674370" Key="LH5FDpx" URL="http://figbug.smugmug.com/Other/2011-05-02-8/21071559_jGHjvS#1675674370_LH5FDpx"/></rsp>

0

Why is the 27, b9 and 0 in the response? And where did the Content-Length header go?

thenickdude · January 18, 2012

figbug wrote: »
I've kinda been ignoring my app for quite a while. A user just reported that it's no longer uploading. Looking at the response I get from the server it looks like this:
HTTP/1.1 200 OK
transfer-encoding: chunked
Why is the 27, b9 and 0 in the response? And where did the Content-Length header go?

The server is sending you a reply using the Chunked transfer encoding:

http://en.wikipedia.org/wiki/Chunked_transfer_encoding

The 27, b9, etc represent the lengths of chunks in the response. Make sure that you're using a HTTP client library which understands chunked encoding.

Extra data in upload response

Comments