1546316 - 204 response replaces the url

Status: RESOLVED INVALID

(Firefox :: Address Bar, defect)

Description

[Eugen Konkov]

Attachment: Kazam_screencast_00000.mp4

User Agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:66.0) Gecko/20100101 Firefox/66.0

Steps to reproduce:

current page is with url

http://feelsafe:3000/api/document_files/9/download?field=content

I input url

feelsafe:3000/api/document_files/9/["2019-03-01 00:00:00+00","2019-04-01 00:00:00+00")/download?field=content

Actual results:

the 204 response come and replaces the current url with old one

Expected results:

url should not be replaced

Also I notice issue when current url is replaced when I press "Refresh page" button on the panel. This happens when I input new url and server for this url is not reached.
Then I press refresh page button to repeat request, but the old url is restored and old page is loaded

Comment 1

[Eugen Konkov]

Comment on attachment 9060030 [details]
Kazam_screencast_00000.mp4

video is not corrupted. It is question: why it cannot be downloaded

Comment 2

[Eugen Konkov]

Attachment: Kazam_screencast_00007.mp4

Other example when "Try Again" button tries different link

Comment 3

[Marcela (Please NI request to Brindusa Tot)]

Hi Eugene Konkov!
I'm not sure if I understood correctly.
I followed these steps and could not reproduce it:
1- Open URL: http://feelsafe:3000/api/document_files/9/download?field=content - an Error message is displayed.
2- I press Try Again button - the initial URL does not change.
3- Press Update button - the URL does not change.

Could you please also test on the latest version of Firefox Nightly and share the results with us?
You can download it from here: https://nightly.mozilla.org/

If there is any other info you can provide to help us figure out how we can reproduce the issue please share it with us.
Thanks for your contribution.

Comment 4

[Eugen Konkov]

of course you do not have http://feelsafe:3000 domain.

Sharp steps:

1. goto google.com
2. Open the address which returns 204

the address is not changed

Comment 5

[Eugen Konkov]

Attachment: _.jpg

Comment 6

[Eugen Konkov]

Attachment: Kazam_screencast_00008.mp4

Comment 7

[Eugen Konkov]

Attachment: Kazam_screencast_00007.mp4

Comment 8

[Eugen Konkov]

Attachment: Kazam_screencast_00006.mp4

Comment 9

[Marcela (Please NI request to Brindusa Tot)]

I tested on OS Ubuntu 16.04 64 bit with latest Nightly 68.0a1, Beta 67.0b19, and Release 66 but I still not able to reproduce it

Comment 10

[Drew Willcoxon :adw]

This is the expected behavior. The HTTP spec says about 204:

The 204 response allows a server to indicate that the action has been
successfully applied to the target resource, while implying that the
user agent does not need to traverse away from its current "document
view" (if any).

https://tools.ietf.org/html/rfc7231#section-6.3.5

See also https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/204

If the browser keeps showing the current document, it makes sense that it should keep showing its URL.

Comment 11

[Eugen Konkov]

@Drew: Probably that is true when user clicks on the form's button. But here I am explicitly change value of address bar.

Comment 12

[Drew Willcoxon :adw]

Yes, but then you press the return key to visit the URL, right? At that point, the text in the urlbar isn't in "edit mode" anymore. Firefox fetches the resource, it's a 204, so it keeps showing the current document and reverts the URL to match it.

Comment 13

[Eugen Konkov]

When I hit ENTER:

1. the address become current document.
2. FF make request to the resource
3. FF get 204

Why it goes back then I do not understand. This is unexpected and ambiguous.
Why when I on "www.i.ua" and input "https://dev.maitre-d.tucha.ua/api/currency_rates/11/[%222019-05-01%22,%222019-06-01%22)" should back to "www.i.ua"?

Also. When I on "www.i.ua" and input "https://dev.maitre-d.tucha.ua/api/currency_rates/11/[%222019-05-01%22,%222019-06-01%22)" and hit ENTER:

1. FF make request to the resource
2. Did not get response
3. I hit refresh page to retry request, but the request is made to old value of address bar.
   this also unexpected and related to current problem.