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
<entryxmlns="http://www.w3.org/2005/Atom">
<in-reply-toref="this-should-cause-a-problem123"xmlns="http://purl.org/syndication/thread/1.0"/>
<content>A lovely little reply via the RESTClient (in FF 21)</content>
</entry>
Expected Outcome:
400 (Bad Request). Server handles response nicely.
Actual Outcome:
500 (Internal Server Error).
I suspect server logs may throw something useful, but how would the client handle this (edge case) scenario? Raised as an enhancement - is there a nicer way to handle this?
The text was updated successfully, but these errors were encountered:
Replication Steps:
Send a message to the API server that posts a reply to message with an invalid ID.
Headers: Basic Authentication [USERNAME/PASSWORD]
Body:
Expected Outcome:
400 (Bad Request). Server handles response nicely.
Actual Outcome:
500 (Internal Server Error).
I suspect server logs may throw something useful, but how would the client handle this (edge case) scenario? Raised as an enhancement - is there a nicer way to handle this?
The text was updated successfully, but these errors were encountered: