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 serving a request for /some/path where the actual resource is /some/path/index.html, the server performs an HTTP 302 redirect to /some/path/, but in the process, it loses any query information the original URL might have had.
Recall that query parts may be used not just by the server but also by client-side Javascript.
Test case
Have a resource such as /some/path/index.html
Start hexo-server
Request /some/path?id=test
Expected result
The user is redirected to /some/path/?id=test (assuming root is /).
Actual result
The user is redirected to /some/path/ and the query information is lost.
The text was updated successfully, but these errors were encountered:
17320
linked a pull request
Oct 5, 2018
that will
close
this issue
When serving a request for
/some/path
where the actual resource is/some/path/index.html
, the server performs an HTTP 302 redirect to/some/path/
, but in the process, it loses any query information the original URL might have had.Recall that query parts may be used not just by the server but also by client-side Javascript.
Test case
/some/path/index.html
hexo-server
/some/path?id=test
Expected result
The user is redirected to
/some/path/?id=test
(assuming root is/
).Actual result
The user is redirected to
/some/path/
and the query information is lost.The text was updated successfully, but these errors were encountered: