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

Chrome deprecation message #58

Closed
scripting opened this Issue Jan 10, 2018 · 1 comment

Comments

Projects
None yet
1 participant
@scripting
Owner

scripting commented Jan 10, 2018

I'm getting this message in the JavaScript console in an app I'm working on.

[Deprecation] Resource requests whose URLs contained both removed whitespace (\n, \r, \t) characters and less-than characters (<) are blocked. Please remove newlines and encode less-than characters from places like element attribute values in order to load these resources. See https://www.chromestatus.com/feature/5735596811091968 for more details.

I don't have much info on it, but it's really weird, it's only objecting on POST messages, otherwise the requests are exactly like all the others that it's letting through.

@scripting

This comment has been minimized.

Show comment
Hide comment
@scripting

scripting Jan 10, 2018

Owner

The post body contained unencoded HTML, which doesn't seem like a problem to me, but I encoded it on the writing side, and decode it on the publishing side, and it works again.

I guess Chrome updated overnight? I hope so. Otherwise I have no idea why this all of a sudden stopped working. One of my least favorite things about programming on the web these days.

Owner

scripting commented Jan 10, 2018

The post body contained unencoded HTML, which doesn't seem like a problem to me, but I encoded it on the writing side, and decode it on the publishing side, and it works again.

I guess Chrome updated overnight? I hope so. Otherwise I have no idea why this all of a sudden stopped working. One of my least favorite things about programming on the web these days.

@scripting scripting closed this Jan 10, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment