Unexpected behavior when Content-Length header is missing
Reported by broglep | April 27th, 2011 @ 08:10 AM
When there is no Content-Length header in the server response, NSObject+ObjectiveResource#updateRemoteAtPath:withResponse: doesn't parse the response although there is one.
A missing Content-Length occours e.g. in case of a gzip encoded response (and gzip encoding is by default accepted by CFNetwork)
See RFC 2616 for more information when Content-Length is not available
Comments and changes to this ticket
-
Alexa Peters January 4th, 2013 @ 06:55 AM
The lucidity in your post is simply striking and I can assume you are an expert on this subject and this could be included in powerpoint presentations.
-
PauletteLeake June 15th, 2020 @ 11:54 AM
I was trying to make my house look better for a long time. Finally I found very good website to check the house guides out. I am so happy! Go and find your household products at homemakerguide.com!
Please Sign in or create a free account to add a new ticket.
With your very own profile, you can contribute to projects, track your activity, watch tickets, receive and update tickets through your email and much more.
Create new ticket
Create your profile
Help contribute to this project by taking a few moments to create your personal profile. Create your profile ยป
Port of Rails' ActiveResource framework to the iPhone.
broglep