1416553 - Feature request: Implement support for 'NextPage' response header

Status: UNCONFIRMED

(Core :: DOM: Core & HTML, defect, P3)

Description

[Eugen Konkov]

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:56.0) Gecko/20100101 Firefox/56.0
Build ID: 20171003144318

Steps to reproduce:

Hi.
As you know when form data is submitted to server. 


Actual results:

The server often after processing redirect to next page.
The browser after receiving server response make next request to the server.
The server got this request, fetch data from database and show some results (often display something that was posted on previous request)

Technically there is no any reason to do this excess redirect. The server may render POST results at once.

The only reason to escape double submission (when user press F5 button)


Expected results:

To prevent user's double submission server after processing POST data from form 


may render results at once plus set 'NextPage' header with same value as it would be in 'Location' header in usual case.

So if in usual case when server response 
```
Location: /processing/result

302 OK
```
and for next request of browser renders content of '/processing/result' page

It will do this at once:
```
NextPage: /processing/results

The processing results...
```

And the browser in turn when see the 'NextPage' header
1. Adjust `window.location` value
2. Do not send POST data when user press refresh button (F5)

Implementing this will save one round trip for network request and on the server side whole route/dispatch process when handling GET request. and the post/redirect/get pattern will not be required anymore


Also, as you may notice, [this is very often problem](https://stackoverflow.com/questions/6320113/how-to-prevent-form-resubmission-when-page-is-refreshed-via-php)  150k view over six years (70 view per day)

thank you.

Comment 1

[Hsin-Yi Tsai (she/her) [:hsinyi]]

Hi Shianyow, this looks like a more necko request. I wonder if this should be on your team's radar.

Comment 2

[Shian-Yow Wu [:swu]]

Hi Eugen, this is not a header defined by public standard, is it supported by any other browsers? What is the status of original problem on other browsers?

Comment 3

[Eugen Konkov]

Hi. It is not defined by public standard; It is not supported by other browsers.

I just open this feature request because think it will be useful (if implemented) and help to save CPU/Network resources.

Now I also found workaround for this problem [here](https://stackoverflow.com/a/47247434/4632019)

But still thinks that work with 'NextPage' header will be simpler and, second, will work on browsers without javascript.

Comment 4

[Shian-Yow Wu [:swu]]

Thanks for the proposal. To consider implementing new HTTP header into browser, we might need it to be proposed as public standard(i.e. IETF RFC/draft) in advance. Ni? Patrick for comments on this.

Comment 5

[Eugen Konkov]

Hi. Is there any progress? May I help with anything?