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
As I pointed our here, it is strange that Leptos with the Actix integration returns 404 on a HEAD request (e.g. curl --head http://127.0.0.1:3000) while it should return 200. Why is this relevant? Services like UptimeRobot reports status "down" for such websites although they are not down. Also the Axum integration works fine, i.e., is inconsistent with the Actix one.
Leptos Dependencies
It can be reproduced with the current leptos-rs/start-actix repo (commit 54b5fb1).
To Reproduce
Steps to reproduce the behavior:
Clone, compile and run leptos-rs/start-actix
Run curl --head http://127.0.0.1:3000
HTTP/1.1 404 Not Found is returned
Expected behavior 200 OK should appear.
The text was updated successfully, but these errors were encountered:
Describe the bug
As I pointed our here, it is strange that Leptos with the Actix integration returns 404 on a HEAD request (e.g.
curl --head http://127.0.0.1:3000
) while it should return 200. Why is this relevant? Services like UptimeRobot reports status "down" for such websites although they are not down. Also the Axum integration works fine, i.e., is inconsistent with the Actix one.Leptos Dependencies
It can be reproduced with the current
leptos-rs/start-actix
repo (commit54b5fb1
).To Reproduce
Steps to reproduce the behavior:
leptos-rs/start-actix
curl --head http://127.0.0.1:3000
HTTP/1.1 404 Not Found
is returnedExpected behavior
200 OK
should appear.The text was updated successfully, but these errors were encountered: