Om de ûnderfining foar jo te ferbetterjen is tydlik de funksjonaliteit dan dizze website troch ûnderhâldswurk beheind. Wannear in artikel jo probleem net oplost en jo in fraach stelle wolle, kin ús stipemienskip jo helpe yn @FirefoxSupport op Twitter en /r/firefox op Reddit.

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

URLs in GET parameters changed in private mode

  • 1 antwurd
  • 0 hawwe dit probleem
  • 16 werjeftes
  • Lêste antwurd fan Aram

Aram
Aram
more options

When in private mode URLs get changed, leading to unexpected results:

http://scripting.com/?url=https://google.com

Will be rewritten to

http://scripting.com/?url=http://google.com

How to reproduce: 1. open a private window 2. enter the example URL (Using Dave Winers non-https as he's an advocate) 3. see the result in the URL bar (the second scheme is changed from https to http)

This only happens when the param has https and the request URL has not (other combinations did not lead to changes). Other browsers did not show this behavior.

When in private mode URLs get changed, leading to unexpected results: http://scripting.com/?url=https://google.com Will be rewritten to http://scripting.com/?url=http://google.com How to reproduce: 1. open a private window 2. enter the example URL (Using Dave Winers non-https as he's an advocate) 3. see the result in the URL bar (the second scheme is changed from https to http) This only happens when the param has https and the request URL has not (other combinations did not lead to changes). Other browsers did not show this behavior.

Alle antwurden (1)

Aram
Aram Fraacheigener
more options

@Dropa

That is what I initially assumed; like some greedy .htaccess rewriting URLs in get parameters.

But if it were a server-side configuration, it would not only happen in private mode (but also in "normal" mode) and it would be a problem in other browsers too.

It appears something to do with "safety" of server URLs: on http://localhost the param is not rewritten.

Bewurke troch Aram op