How are parts of video request and process? #1489

barvirm · 2022-10-20T14:10:34Z

barvirm
Oct 20, 2022

Hello, I'm trying to stream a video from FS through the Axum server to the browser and use browser native video player.

Here is my naive version, but it completely fails.
I know that I should respond with 206 when I get some Ranges.
I already tried it and it doesn't help.
Can someone help me clarify the communication in this process?

Request is for Content length and checks if ranges are accepted -> StatusCode::OK
- I assume
Request is with range close to the end -> StatusCode::PartialContent
- I don't understand
Request is for the beginning of the video

I would rather explanation how it works then fixing my code 👍
My sample video: https://www.sample-videos.com/video123/mp4/720/big_buck_bunny_720p_30mb.mp4

use std::io::SeekFrom;
use std::net::SocketAddr;

use async_trait::async_trait;
use axum::body::{Body, StreamBody};
use axum::extract::FromRequestParts;
use axum::http::request::Parts;
use axum::http::{header, Request, StatusCode};
use axum::response::IntoResponse;
use axum::routing::get;
use axum::Router;
use http_range_header::ParsedRanges;
use tokio::fs::File;
use tokio::io::AsyncSeekExt;
use tokio_util::io::ReaderStream;

struct RangesHeader(ParsedRanges);

#[async_trait]
impl<S> FromRequestParts<S> for RangesHeader
where
    S: Send + Sync,
{
    type Rejection = (StatusCode, &'static str);

    async fn from_request_parts(parts: &mut Parts, _state: &S) -> Result<Self, Self::Rejection> {
        let range_header_str = parts
            .headers
            .get(header::RANGE)
            .ok_or((StatusCode::BAD_REQUEST, "`Range` header is missing"))?
            .to_str()
            .map_err(|_| {
                (StatusCode::BAD_REQUEST, "`Authorization` header contains invalid characters")
            })?;

        let ranges = http_range_header::parse_range_header(range_header_str).unwrap();

        Ok(Self(ranges))
    }
}

#[tokio::main]
async fn main() {
    let app = Router::new().route("/hello.mp4", get(handler));

    let addr = SocketAddr::from(([127, 0, 0, 1], 3000));
    axum::Server::bind(&addr).serve(app.into_make_service()).await.unwrap();
}

async fn handler(ranges: Option<RangesHeader>, request: Request<Body>) -> impl IntoResponse {
    let filename = "sample_video.mp4";
    let mut file = File::open(filename).await.unwrap();
    let meta = file.metadata().await.unwrap();

    if let Some(RangesHeader(parsed_ranges)) = ranges {
        let ranges = parsed_ranges.validate(meta.len()).unwrap();
        if ranges.len() != 1 {
            panic!("Multiple ranges not implemented right now")
        }

        if let Some(range) = ranges.first() {
            file.seek(SeekFrom::Start(*range.start())).await.unwrap();
        }
    }

    let body = StreamBody::new(ReaderStream::new(file));

    (
        StatusCode::OK,
        [
            (header::CONTENT_TYPE, "video/mp4".to_string()),
            (header::ACCEPT_RANGES, "bytes".to_string()),
            (header::CONTENT_LENGTH, meta.len().to_string()),
        ],
        body,
    )
}

Stefan99353 · 2023-04-15T09:53:41Z

Stefan99353
Apr 15, 2023

Hi,

I just had the same "problem" and found a solution. It is actually really easy.
Since axum is compatible with tower stuff, we can just use that.

You need to add tower-http to your procejt with the feature fs and tower:

[dependencies]
tower = "0.4"
tower-http = { version = "0.4", features = ["fs"] }

Your new code would look something like this:

use tower::ServiceExt;

async fn handler(request: Request<Body>) -> impl IntoResponse {
    let filename = "sample_video.mp4";

    let serve_file = tower_http::services::fs::ServeFile::new(filename);
    serve_file.oneshot(request).await
}

ServeFile
Axum example

1 reply

davidpdrsn Apr 15, 2023
Collaborator

You can also do .route_service("/foo", tower_http::services::fs::ServeFile::new("sample_video.mp4"))

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Uh oh!

How are parts of video request and process? #1489

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Replies: 1 comment 1 reply

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Uh oh!

{{title}}

Uh oh!

Uh oh!

{{editor}}'s edit

{{editor}}'s edit

Uh oh!

Select a reply

Uh oh!

How are parts of video request and process? #1489

Uh oh!

Uh oh!

barvirm Oct 20, 2022

Replies: 1 comment · 1 reply

Uh oh!

Uh oh!

Stefan99353 Apr 15, 2023

Uh oh!

Uh oh!

davidpdrsn Apr 15, 2023 Collaborator

barvirm
Oct 20, 2022

Replies: 1 comment 1 reply

Stefan99353
Apr 15, 2023

davidpdrsn Apr 15, 2023
Collaborator