GitHub is home to over 20 million developers working together to host and review code, manage projects, and build software together.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
Already on GitHub? Sign in to your account
While using AFCache I noticed that apparently UIWebView gets confused when the text encoding is part of the MIME type (aka content type) field of a NSURLResponse. This can happen when the original request was responded by a web application with e.g. the perfectly legal header Content-type: text/html; charset=utf-8.
Content-type: text/html; charset=utf-8
I fixed this by implementing a simple parser for MIME types per RFC 2616 (see section 3.7) and using that one to split the content type and the text encoding.
Please let me know if you like the patch. If further works needs to be done to get this into your branch, I'd be happy to do that.
(At least) UIWebView instances get confused when the content encoding…
is part of the MIMEType property of a NSURLResponse. Splitting the MIME type
and passing the conding using textEncodingName fixes this.
We probably need to figure out a more solid way to parse the MIME type.
The name of the manifest is actually manifest.afcache.
Make the unit testing target compile.
RFC 2616 conforming parser for Internet Media Types.
Committing pending changes regarding the RFC 2616 parser.
These changes should have been part of the previous commit but
somehow got lost somewhere.
This should be added. It worked great to eliminate the problem of UIWebview showing HTML code instead of the actual webpage due to mime types not being recognized.
Parse MIME type from the manifest file.