-
SummaryI have a very simple Axum server I get 404 not found error for my-script.js: Problem doesn't occur when the page is served using VSCode live server. What am i doing wrong? Thanks! === src/main.rs === async fn main() -> Result<()> {
// Create top level router
let routes_all = Router::new()
.route("/", get(root))
.nest_service("/home", get_service(ServeDir::new("assets"))); // <<------
let api_server_addr = "localhost:3000";
// Create a TCP listener
let listener = tokio::net::TcpListener::bind(api_server_addr).await?;
// Start serving the app
println!("API server listening on: {api_server_addr}");
axum::serve(listener, routes_all).await?;
Ok(()) // main() completed with no errors
}
// endregion: ---- MAIN ----
async fn root() -> Html<String> {
Html("<h1> Hello from the root route</h1>".to_string())
}=== assets/index.html === <!DOCTYPE html>
<html lang="en">
<head>
<title>Test</title>
<meta charset='utf-8'>
<meta name="viewport" content="width=device-width, initial-scale=1">
</head>
<body>
<p>Hello from index.html</p>
<script src="my-script.js"></script> <!-- Cant find this file -->
</body>
</html>axum versionaxum = "0.7.5", tower-http = {version = "0.5.2", features = ["fs"]} |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 4 replies
-
|
How are you testing this? If you're opening the page in a browser at |
Beta Was this translation helpful? Give feedback.
-
|
jplatte: Thanks for looking at this. You make an interesting observation. I test by opening the page http://127.0.0.1:3000/home let routes_all = Router::new()
.route("/", get(root))
.nest_service("/home", get_service(ServeDir::new("assets"))); // <<------ will serve the contents of the assets directory on a route named /home . However, your observation about the error message prompted me to try serving the directory from the root route '/', like this: let routes_all = Router::new()
//.route("/", get(root)) // Commented out to avoid conflicting
.nest_service("/", get_service(ServeDir::new("assets"))); // Moved from route "/home" to "/"And that works. |
Beta Was this translation helpful? Give feedback.
-
|
I suspect this could be another case of the When you called You could try calling |
Beta Was this translation helpful? Give feedback.
-
|
Ok - resolved (sort of). Suppose one has a directory containing an index.html file which has links to other files in that directory such as stylesheets, javascript, images, etc. For example, if assets/index.html references assets/my-script.js like this: <script src="my-script.js"></script> and we use nest_service to serve the assets directory on the route /home like this: let routes_all = Router::new()
.route("/", get(root))
.nest_service("/home", get_service(ServeDir::new("assets"))); then one must modify the tag to this: <script src="home/my-script.js"></script>My code works now, but to me it doesn't make sense that this should be the way nest_service/ServeDir work. |
Beta Was this translation helpful? Give feedback.
-
|
Ignore my reply directly above this. There is no need for any changes to the paths to files in the html. .nest_service("/home/", get_service(ServeDir::new("assets")));and browsing to http://127.0.0.1:3000/home/ solves the problem |
Beta Was this translation helpful? Give feedback.
I suspect this could be another case of the
/home/vs/homenesting issue.When you called
/home, the directory is/so the browser tried to fetch/my-script.js. If you had usednest_service("/home/", ...);and calledlocalhost/home/instead, I think it would correctly use the relative path as/home/my-script.js.You could try calling
locahost/home/index.html, I think that version should work. I didn't try to run any code though, so I'm just extrapolating and guessing here.