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
After #38 has been closed, we have now the situation where the DefaultRejectionHandler discards the entity but the DefaultExceptionHandler does not.
In my opinion, it should behave the same way, discarding the entity.
What do you think?
The text was updated successfully, but these errors were encountered:
jlprat
added
0 - new
Ticket is unclear on it's purpose or if it is valid or not
discuss
Tickets that need some discussion before proceeding
labels
Jun 20, 2018
That seems sensible to me. One consideration here is that in the ExceptionHandler, it seems the chance is much higher that the exception occurs when the route has already consumed the entity, or (worse) when it has partially consumed the entity. Do we have a way to deal with those cases?
Yes, I was also thinking about this, that exceptions are more likely to occur when the entity is (half) consumed. But I guess discarding the entity always works, which problems do you see with discarding a partly consumed entity?
jlprat
added a commit
to jlprat/akka-http
that referenced
this issue
Sep 13, 2018
After #38 has been closed, we have now the situation where the
DefaultRejectionHandler
discards the entity but theDefaultExceptionHandler
does not.In my opinion, it should behave the same way, discarding the entity.
What do you think?
The text was updated successfully, but these errors were encountered: