Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

HTTP Response Content-Type parsing fail when no encoding #49

Closed
mehlah opened this issue Jul 28, 2011 · 1 comment
Closed

HTTP Response Content-Type parsing fail when no encoding #49

mehlah opened this issue Jul 28, 2011 · 1 comment

Comments

@mehlah
Copy link
Contributor

mehlah commented Jul 28, 2011

Parsing an HTTP Response with a Content-Type=application/json should store the response type as application/json.

Instead, Response->type = text/html (default constructed value)

and, parsing a Content-Type=application/json;charset=utf-8 works perfectly.

@gwoo gwoo closed this as completed in 6ea6cdc Jul 28, 2011
@Ciaro
Copy link
Contributor

Ciaro commented Jul 28, 2011

On a sidenote: RequestTest::testType() only seems to pass on Apache webservers. It returns nothing ('' instead of 'html') on for example IIS and Nginx (probably all other webservers?).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants