Avatar for Username

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

This thread was archived. Please ask a new question if you need help.

What is the expected navigation behavior of a 204 response to a form post.

  • 1 reply
  • 0 have this problem
  • 8 views
  • Last reply by grimzecho

grimzecho
grimzecho
more options

According to Mozilla, the 204 No Content response "indicates that a request has succeeded but that the client doesn't need to navigate away from its current page".

However, when Firefox receives such a code in response to a status code, it triggers the `window.onbeforeunload` event and any associated handlers. This has side-effects such as closing any open websocket connections associated with the page, re-rendering the DOM (which fires various lifecycle methods in single page apps), and other similar activities that are generally associated with navigating away from a page.

Is this behavior intended or documented anywhere? Or should it be considered a bug?

According to Mozilla, the [https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204 204 No Content] response "indicates that a request has succeeded but that the client doesn't need to navigate away from its current page". However, when Firefox receives such a code in response to a status code, it triggers the `window.onbeforeunload` event and any associated handlers. This has side-effects such as closing any open websocket connections associated with the page, re-rendering the DOM (which fires various lifecycle methods in single page apps), and other similar activities that are generally associated with navigating away from a page. Is this behavior intended or documented anywhere? Or should it be considered a bug?

All Replies (1)

grimzecho
grimzecho Question owner
more options

--edit-- There is a typo. The first sentence of the second paragraph should read: "However, when Firefox receives such a code in response to a form post, it triggers ..."