We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
SecureCQ version: 1.3.1
At the same time
$ curl -v https://dev.example.com/system/console/ -o /dev/null ... > GET /system/console HTTP/1.1 > Host: dev.example.com > User-Agent: curl/7.53.1 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Content-Type: text/html; charset=iso-8859-1 < Date: Mon, 04 Sep 2017 12:37:08 GMT < Location: https://dev.example.com/system/console/ < Server: Apache < Content-Length: 252 < Connection: keep-alive
When I follow redirects I get 404
$ curl -v https://dev.example.com/system/console/ -o /dev/null > GET /system/console HTTP/1.1 > Host: dev.example.com > User-Agent: curl/7.53.1 > Accept: */* > < HTTP/1.1 301 Moved Permanently < Content-Type: text/html; charset=iso-8859-1 < Date: Mon, 04 Sep 2017 12:38:05 GMT < Location: https://dev.example.com/system/console/ < Server: Apache < Content-Length: 252 < Connection: keep-alive < > GET /system/console/ HTTP/1.1 > Host: dev.example.com > User-Agent: curl/7.53.1 > Accept: */* > < HTTP/1.1 404 Not Found < Accept-Ranges: bytes < Content-Type: text/html; charset=UTF-8 < Date: Mon, 04 Sep 2017 12:38:05 GMT < Last-Modified: Mon, 04 Sep 2017 10:35:38 GMT < Server: Apache < X-Content-Type-Options: nosniff < X-Frame-Options: SAMEORIGIN < X-Request-ID: Wa1JLZ--61UQKao-HPCBDAAAAXY < Content-Length: 83201 < Connection: keep-alive
All in all, rules that rely on HTTP status codes should follow redirects before producing final status.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
SecureCQ version: 1.3.1
At the same time
When I follow redirects I get 404
All in all, rules that rely on HTTP status codes should follow redirects before producing final status.
The text was updated successfully, but these errors were encountered: