You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Responses are currently required to be hal+json. The API we consume returns a 201 without data and a http header for a new location when we do a _post. The request is successful but Hyperclient gives a InvalidRepresentationError due to the response not being hal+json.
This works in v0.8.5 but not in the latest version due to 1c7dc4c
I'll provide a failing test later.
The text was updated successfully, but these errors were encountered:
Thanks, overriding response content type works. I assumed the problem was due to the empty body.
client.connection do |conn|
conn.response :hal_json
end
This is the first hal-json API I'm using so not sure what the norm is. If it is normal to retrieve a response like this with empty body and without content-type then perhaps this user case should be more explicit in the readme (I can provide a PR for that). If this is some uncommon scenario then no worries.
Responses are currently required to be
hal+json
. The API we consume returns a 201 without data and a http header for a new location when we do a_post
. The request is successful but Hyperclient gives aInvalidRepresentationError
due to the response not beinghal+json
.This works in v0.8.5 but not in the latest version due to 1c7dc4c
I'll provide a failing test later.
The text was updated successfully, but these errors were encountered: