-
Notifications
You must be signed in to change notification settings - Fork 43
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
Delete Response has false Content-Type #25
Comments
Hi @benno208, Thanks for reporting this! I just pushed a new version of the library that shouldn't have this problem; can you check? Here's how it should behave now. First, the server should no longer send, and clients no longer need to indicate that they'll As for the The story with So, in the end, here's what this adds up to:
|
First thing after updating to 2.3.0:
|
Weird.... I just did a fresh install and things appear to be running fine. Can you give me the stack trace for that error? |
I did a complete install. Now everything seems to be fine. When I do a POST I get
and on PATCH:
|
What's the Accept header you're sending? For some reason, it's thinking that generic JSON should be used rather than the JSON API media type. |
I'm sending the following headers:
And I'm testing for:
|
Damn, I clicked the false button... |
Very weird...what you posted earlier should have worked (and was working for me). However, I've just pushed a new version of the library that removes the automatically-appended charset parameter all together. So now you should be able to send a request with:
And get back
There's a test for this behavior and, on my machine at least, it's passing. Let me know if you're still experiencing problems after upgrading to the latest version :) |
Now, everything works like expected. Thanks! |
Awesome! |
I'm doing some testing with supertest:
I get the following error:
GET, POST and PATCH work very well
The text was updated successfully, but these errors were encountered: