search

strongloop / strong-remoting

Communicate between objects in servers, mobile apps, and other servers.
www.strongloop.com
Other
105 stars 93 forks source link

Incorrect content type in 204 responses (expected XML) #258

Closed bajtos closed 8 years ago

bajtos commented 8 years ago

At the moment, we always return the content header as JSON when there isn't any response payload, even if the XML output is enabled and the client requested it.

pulkitsinghal commented 8 years ago

Where is it in https://waffle.io/strongloop/loopback?

bajtos commented 8 years ago

Where is it in https://waffle.io/strongloop/loopback?

@pulkitsinghal This issue is sitting in the Top of Backlog column, which is our list of candidates to be planned for the next sprint.

bajtos commented 8 years ago

At the moment, we always return the content header as JSON when there isn't any response payload, even if the XML output is enabled and the client requested it.

I have released the fix in strong-remoting@2.23.2.

@pulkitsinghal enjoy :)