Apparently, NSURLConnection
automatically decodes gzipped responses. But, can it gzip encode its requests? If so, how? Or, does it do this automatically too?
相关问题
- CALayer - backgroundColor flipped?
- Core Data lightweight migration crashes after App
- Core Data lightweight migration crashes after App
- How can I implement password recovery in an iPhone
- State preservation and restoration strategies with
相关文章
- 现在使用swift开发ios应用好还是swift?
- UITableView dragging distance with UIRefreshContro
- Could I create “Call” button in HTML 5 IPhone appl
- TCC __TCCAccessRequest_block_invoke
- Where does a host app handle NSExtensionContext#co
- xcode 4 garbage collection removed?
- Unable to process app at this time due to a genera
- Swift - hide pickerView after value selected
An HTTP request body cannot be gzipped at the protocol level, as there is no way for the client to know whether the server supports that or not; it works for the server response because the client indicates in the request whether a gzipped response body can be accepted. (It could be done in the future something like how
Expect: 100-continue
works, but that's not the situation we're faced with today).At the application level, you certainly could gzip the request body. But that would be outside the realm of NSURLConnection.
I'm usually all for using NSURLRequests over ASIHTTPRequests, but ASI does handle this case. HTTP request compression isn't something you can use all the time safely. You can't detect whether a server will handle this correctly on a route. Even if you get Apache setup to handle this correctly it will fail when making requests on different modules since they might not handle it correctly.
http://allseeing-i.com/ASIHTTPRequest/How-to-use#using_gzip_to_compress_request_bodies