Re-click on the "Send Request" can cause an error if the result of the first request received the header ETag. A second request is transmitted header "If-None-Match", but the server does not correctly handle 304 redirects (Not Modified).
Solutions:
To handle 304 redirect on the server before sending the response
To prevent cache on the client side
To handle 304 on the server and add the option "cache" on the frontend
Re-click on the "Send Request" can cause an error if the result of the first request received the header
ETag
. A second request is transmitted header "If-None-Match", but the server does not correctly handle 304 redirects (Not Modified).Solutions:
@greabock aware of the problem.