You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Repository navigation
This repository was archived by the owner on Nov 6, 2023. It is now read-only.
Target gets different HTTP code in test depending on whether another specific target is present #7711
When fetch-test.sh runs against a ruleset with only targetforum, forum gets a 200. If I add a second targetwww either before or after forum, forum gets a 502. If instead I add target^, forum gets a 200.
In other words, one target passes the test or doesn't based on whether another specific target is in the ruleset. This happens consistently. I have no explanation. This comes from pull request #5390.
So here we can see that https://forum.glavbukh.ru is issued a normal redirect to http://www.glavbukh.ru/forum, which exists and returns a 200 response. But because of the other rule, this is in turn redirected via HTTPSE to https://www.glavbukh.ru/forum, which does not exist, and returns a 502 response. Thus the error.
What's interesting here is that the non-parity between http://www.glavbukh.ru and https://www.glavbukh.ru is only discovered through the existence of a separate target, because of the fact that it generates a new test url which is transformed by the original target.
Activity
jeremyn commentedon Nov 29, 2016
@fuglede @gloomy-ghost @Hainish @J0WI FYI.
Hainish commentedon Nov 29, 2016
@jeremyn looking into this now
Hainish commentedon Nov 30, 2016
If we set the
loglevelintest/rules/http.checker.configtodebug, we see the following withgood.xml:And with
bad.xml:So here we can see that
https://forum.glavbukh.ruis issued a normal redirect tohttp://www.glavbukh.ru/forum, which exists and returns a200response. But because of the other rule, this is in turn redirected via HTTPSE tohttps://www.glavbukh.ru/forum, which does not exist, and returns a502response. Thus the error.Hainish commentedon Nov 30, 2016
What's interesting here is that the non-parity between
http://www.glavbukh.ruandhttps://www.glavbukh.ruis only discovered through the existence of a separate target, because of the fact that it generates a new test url which is transformed by the original target.