1
0
mirror of https://github.com/fafhrd91/actix-web synced 2024-11-24 16:32:59 +01:00
actix-web/guide/src/qs_12.md

47 lines
1.3 KiB
Markdown
Raw Normal View History

2017-12-02 09:24:26 +01:00
# Static file handling
2017-12-04 03:15:09 +01:00
## Individual file
It is possible to serve static files with custom path pattern and `NamedFile`. To
2017-12-05 01:26:40 +01:00
match path tail we can use `[.*]` regex.
2017-12-04 03:15:09 +01:00
```rust
2017-12-05 01:26:40 +01:00
# extern crate actix_web;
2017-12-04 03:15:09 +01:00
use actix_web::*;
use std::path::PathBuf;
fn index(req: HttpRequest) -> Result<fs::NamedFile> {
let path: PathBuf = req.match_info().query("tail")?;
Ok(fs::NamedFile::open(path)?)
}
fn main() {
2017-12-06 20:00:39 +01:00
Application::new("/")
.resource(r"/a/{tail:.*}", |r| r.method(Method::GET).f(index))
2017-12-04 03:15:09 +01:00
.finish();
}
```
## Directory
2017-12-05 01:26:40 +01:00
To serve files from specific directory and sub-directories `StaticFiles` could be used.
2017-12-08 21:29:28 +01:00
`StaticFiles` could be registered with `Application::resource` method.
`StaticFiles` requires tail named path expression for resource registration.
And this name has to be used in `StaticFile` constructor.
2017-12-04 03:15:09 +01:00
```rust
2017-12-05 01:26:40 +01:00
# extern crate actix_web;
use actix_web::*;
2017-12-04 03:15:09 +01:00
fn main() {
2017-12-06 20:00:39 +01:00
Application::new("/")
2017-12-08 21:29:28 +01:00
.resource("/static/{tail:.*}", |r| r.h(fs::StaticFiles::new("tail", ".", true)))
2017-12-04 03:15:09 +01:00
.finish();
}
```
2017-12-08 21:29:28 +01:00
First parameter is a name of path pattern. Second parameter is a base directory.
Third parameter is *show_index*, if it is set to *true*
2017-12-04 03:15:09 +01:00
directory listing would be returned for directories, if it is set to *false*
then *404 Not Found* would be returned instead of directory listing.