Pretraži podršku

Izbjegni prevare podrške. Nikad te nećemo tražiti da nas nazoveš, da nam pošalješ telefonski broj ili da podijeliš osobne podatke. Prijavi sumnjive radnje pomoću opcije „Prijavi zlouporabu”.

Saznaj više

URLs in GET parameters changed in private mode

  • 1 odgovor
  • 0 ima ovaj problem
  • 16 prikaza
  • Posljednji odgovor od 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.

Svi odgovori (1)

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.

Izmjenjeno od Aram