Avatar for Username

搜索 | 用户支持

防范以用户支持为名的诈骗。我们绝对不会要求您拨打电话或发送短信，及提供任何个人信息。请使用“举报滥用”选项报告涉及违规的行为。

详细了解

话题已存档。 如果需要帮助请提出新问题。

URLs in GET parameters changed in private mode

  • 1 个回答
  • 0 人有此问题
  • 16 次查看
  • 最后回复者为 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.

所有回复 (1)

Aram
Aram 提问者
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.

由Aram于修改