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
When making a request with query parameters, for example:
curl http://<ip>/test?foo=bar
the server logs and responses do not show the query parameters at all. In the logs, only the path /test is displayed without the ?foo=bar part:
[2025-05-18 16:10:43] - 404 - GET /test
I don't know if it was intended that way, but it just makes it difficult to debug requests.
As shown in the image below, the server does not reflect any query parameters in the log or response:
And here is for example the output from another http server, where these parameters are displayed:
Environment:
simple-http-server version: 0.6.10 and 0.6.12(latest)
OS: arch linux
Perhaps it would make sense to include at least a --verbose or --debug option that logs the full request URI, including query parameters. That could be really helpful for debugging and inspecting requests.
The text was updated successfully, but these errors were encountered:
When making a request with query parameters, for example:
curl http://<ip>/test?foo=bar
the server logs and responses do not show the query parameters at all. In the logs, only the path /test is displayed without the ?foo=bar part:
[2025-05-18 16:10:43] - 404 - GET /test
I don't know if it was intended that way, but it just makes it difficult to debug requests.
As shown in the image below, the server does not reflect any query parameters in the log or response:
And here is for example the output from another http server, where these parameters are displayed:
Environment:
Perhaps it would make sense to include at least a --verbose or --debug option that logs the full request URI, including query parameters. That could be really helpful for debugging and inspecting requests.
The text was updated successfully, but these errors were encountered: