This project is archived and is in readonly mode.
Error sending empty Content-Type instrumentation.rb#22
-
Kenn Ejima
I had the same problem. In our case, some of our API client developers use Titanium and we have no control over what they choose, so I agree that at least we need an appropriate error (probably 400 Bad Request) raised that should be catched to respond an appropriate error JSON message to the client.
Or, to just go ahead without content type, probably Fjan's patch in this ticket could fix this problem as a more robust, generic fallback-to-html approach, to deal with future misbehaving clients?
#6022 Content negotiation fails for some */* headers (regression)
-
Neeraj Singh
- State changed from new to open
- Assigned user set to José Valim
- Importance changed from to Low
Fix is here. See the last commit.