Aioros 的回应
开发者回应
发布于 5 年前It shouldn't be necessary, I'll see if I can reproduce the problem. Thanks for letting me know.
35 条评价
- 评分 5 / 5来自 天灭中共退党团队保平安,1 个月前
- 评分 2 / 5来自 weilinfox,1 年前
- 评分 2 / 5来自 Firefox 用户 12995607,2 年前The extension rewrites the URL to http://«ip»/«hostname»/, and I assume some internal magic to remove the hostname from the path again and to set the correct Host: header.
The problem with this approach is that it breaks some sites; href="/foo", src="/assets/bla.css" removes the /hostname part from the URL, causing these kind of links to break.
I would be interested in a version of this that does not rewrite the URL, but I can imagine that will be hard to do within Firefox' extension API. - 评分 1 / 5来自 elgarfo,2 年前
- 评分 5 / 5来自 eathtespagheti,3 年前
- 评分 1 / 5来自 Firefox 用户 17513812,3 年前
- 评分 5 / 5来自 Firefox 用户 16610910,3 年前
- 评分 5 / 5来自 Nikolay Iglev,3 年前
- 评分 4 / 5来自 Olivier BOËL,3 年前Very useful! Congrats & thanks!
Would be nice to have the option to avoid changing the URL in the browser as some SPA rely on it. - 评分 1 / 5来自 Firefox 用户 12603543,3 年前
- 评分 5 / 5来自 레몬라임,4 年前
- 评分 5 / 5来自 Tsvyatko,4 年前
- 评分 5 / 5来自 Firefox 用户 14331125,4 年前
- 评分 5 / 5来自 Ilya,4 年前
- 评分 5 / 5来自 Arash,4 年前
- 评分 2 / 5来自 David,5 年前The extension seems to just rewrite the URL to replace the domain name with an IP address before making a request. When I add a rule to point www.example.com at 127.0.0.1, and type https://www.example.com in the address bar, the browser just goes to https://127.0.0.1, instead of what I'd expect it to do which was direct the browser to connect to 127.0.0.1 but keep the Host header as www.example.com. It might be useful for people testing non-HTTPS sites without a virtual hosting configuration, but I'm not in that situation so this extension doesn't help with my needs at all.
- 评分 2 / 5来自 henrique.abreu,5 年前Pop-up to add new rules is really crappy, closes all the time, does not have a way to update in bulk... and tweaking more settings is required to make it work.