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

use websocket text/plain as default content-type #504

Closed
jknack opened this issue Oct 15, 2016 · 0 comments
Closed

use websocket text/plain as default content-type #504

jknack opened this issue Oct 15, 2016 · 0 comments
Milestone

Comments

@jknack
Copy link
Member

jknack commented Oct 15, 2016

The default content-type was */* which was causing some troubles. Due a websocket is use to receive/send text it makes more sense to set default content type to text/plain

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

No branches or pull requests

1 participant