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
When state changing requests hit the server via GET request method, we need to handle them (and change state) on the read side. This breaks the approach of separating read / write by their meanings.
In order to handle such a state changing GET request correctly, add configurable request bypasses to internally reroute the read request to a write request, so that a write request handler is responsible for handling the request and the business logic is kept separated.
When state changing requests hit the server via GET request method, we need to handle them (and change state) on the read side. This breaks the approach of separating read / write by their meanings.
In order to handle such a state changing GET request correctly, add configurable request bypasses to internally reroute the read request to a write request, so that a write request handler is responsible for handling the request and the business logic is kept separated.
The bypasser will - if necessary - create a new request info object that is matched against the normal routing definitions.
The text was updated successfully, but these errors were encountered: