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

Content-type could use its own verifier #11

Open
macosforgebot opened this issue Jul 12, 2010 · 2 comments
Open

Content-type could use its own verifier #11

macosforgebot opened this issue Jul 12, 2010 · 2 comments
Assignees
Milestone

Comments

@macosforgebot
Copy link

@macosforgebot macosforgebot commented Jul 12, 2010

douglm@… originally submitted this as ticket:387


Tests fail because the content-type header value doesn't match but is actually valid, e.g. g test for

text/calendar;charset=utf-8

and receive

text/calendar; charset=UTF-8

The space(s) after the semi-colon are valid as is the UC "UTF-8"

This might be complicated enough to justify its own verifier

@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Aug 1, 2011

@wsanchez originally submitted this as comment:1:⁠ticket:387

  • Radar deleted
  • Priority changed from 5: Not set to 2: Expected
@macosforgebot
Copy link
Author

@macosforgebot macosforgebot commented Nov 30, 2011

@wsanchez originally submitted this as comment:2:⁠ticket:387

  • Milestone set to Later
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants
You can’t perform that action at this time.