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

Encourage console warning for method normalization #259

Closed
annevk opened this issue Mar 23, 2016 · 3 comments
Closed

Encourage console warning for method normalization #259

annevk opened this issue Mar 23, 2016 · 3 comments
Labels

Comments

@annevk
Copy link
Member

@annevk annevk commented Mar 23, 2016

If we log a warning whenever https://fetch.spec.whatwg.org/#concept-method-normalize is invoked, perhaps that'll teach folks that HTTP method names are case-sensitive.

@wanderview @tyoshino any interest in adding such a warning? You probably only want to do it once per global or some such, to avoid spamming too much.

@annevk annevk mentioned this issue Mar 23, 2016
@tyoshino

This comment has been minimized.

Copy link
Member

@tyoshino tyoshino commented Mar 23, 2016

This algorithm runs only for input from script via init, right? Then, once people see a warning, they can respond to it just by fixing their code.

and, yeah, we can choose to show it only once.

I think it's good.

I'm also interested in showing a warning when a Headers object rejects append of some header silently due to the guard set to it. Should I file another issue for it?

@annevk

This comment has been minimized.

Copy link
Member Author

@annevk annevk commented Mar 23, 2016

We can do both in this issue. I just need to figure out what kind of wording HTML uses to encourage reporting things to the console and then I'll update both places.

@annevk

This comment has been minimized.

Copy link
Member Author

@annevk annevk commented Dec 13, 2018

Trying to think this through again, I think this would end up being too noisy so implementations should probably not issue a warning here. This will have to be a quirk developers discover on their own. (Happy to discuss further though in follow-up comments.)

@annevk annevk closed this Dec 13, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Linked pull requests

Successfully merging a pull request may close this issue.

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