This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

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

Wannan tattunawa ta zama daɗaɗɗiya. Yi sabuwar tambaya idan ka na bukatar taimako.

URLs in GET parameters changed in private mode

  • 1 amsa
  • 0 sa na da wannan matsala
  • 16 views
  • Amsa ta ƙarshe daga 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.

All Replies (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.

An gyara daga Aram