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
Describe the bug
Skipper does not support parsing of URL queries that contain semicolon, but logs an error if clients send semicolons. Logged errors should be actionable, which in this context is not the case since this is something the client does. It's not an error from Skipper's perspective.
Expected behavior
Log level of info would potentially (if a log message is actually required) make more sense in this case.
Observed behavior
with Skipper v0.13.185 time="2022-03-18T09:20:32Z" level=error msg="http: URL query contains semicolon, which is no longer a supported separator; parts of the query may be stripped when parsed; see golang.org/issue/25192\n"
The text was updated successfully, but these errors were encountered:
Describe the bug
Skipper does not support parsing of URL queries that contain semicolon, but logs an error if clients send semicolons. Logged errors should be actionable, which in this context is not the case since this is something the client does. It's not an error from Skipper's perspective.
Expected behavior
Log level of info would potentially (if a log message is actually required) make more sense in this case.
Observed behavior
with Skipper v0.13.185
time="2022-03-18T09:20:32Z" level=error msg="http: URL query contains semicolon, which is no longer a supported separator; parts of the query may be stripped when parsed; see golang.org/issue/25192\n"
The text was updated successfully, but these errors were encountered: