Route matching issue: web::resource() routes register but don't match incoming requests

[markur]

Actix-web Route Matching Issue: Routes Register But Return 404

Environment

• Actix-web: 4.x
• Rust: 1.91.1
• Framework Pattern: Using web::resource() for dynamic path routes

Problem

I'm registering video frame extraction endpoints in Actix-web, but they return HTTP 404 despite being successfully registered at startup. The handler functions are never called.

Evidence That Routes ARE Registered

Startup logs confirm both routes register successfully (4 times, once per worker):

2026-03-11T00:34:22.291704Z INFO backend::video_handler: ✅ Successfully registered 2 routes:
  - GET /api/admin/products/{id}/video-info
  - POST /api/admin/products/{id}/extract-frame
(repeats 3 more times for remaining workers)

Code: Route Registration Pattern (BROKEN)

video_handler.rs:

pub fn video_routes(cfg: &mut web::ServiceConfig) {
    cfg
        .service(
            web::resource("/api/admin/products/{id}/video-info")
                .route(web::get().to(get_video_info))
        )
        .service(
            web::resource("/api/admin/products/{id}/extract-frame")
                .route(web::post().to(extract_frame))
        );
}

main.rs (App configuration):

App::new()
    .configure(admin_products::admin_product_routes)  // ✅ Works fine
    .configure(video_handler::video_routes)            // ❌ Returns 404
    // ... other routes

Code: Working Pattern for Comparison

admin_products.rs (this DOES work):

pub fn admin_product_routes(cfg: &mut web::ServiceConfig) {
    cfg.service(
        web::scope("/api/admin/products")
            .route("", web::get().to(list_products))
            .route("", web::post().to(create_product))
            .route("/{id}", web::get().to(get_product))
            .route("/{id}", web::delete().to(delete_product))
        );
}

Handler Signatures

Video handler (never called):

pub async fn get_video_info(
    _state: web::Data<Arc<AppState>>,
    path: web::Path<i32>,
    query: web::Query<std::collections::HashMap<String, String>>,
) -> Result<web::Json<VideoInfoResponse>, AppError> {
    tracing::info!("get_video_info: Starting...");  // ← This log NEVER appears
    // ... handler code
}

pub async fn extract_frame(
    _state: web::Data<Arc<AppState>>,
    path: web::Path<i32>,
    body: web::Json<ExtractFrameRequest>,
) -> Result<web::Json<ExtractFrameResponse>, AppError> {
    tracing::info!("extract_frame: Starting extraction...");  // ← This log NEVER appears
    // ... handler code
}

Test Evidence

Request:

curl -v -X POST "http://localhost:3000/api/admin/products/1/extract-frame" \
  -H "Content-Type: application/json" \
  -d '{"video_url": "/uploads/products/video.mp4", "timestamp": 5.0, "format": "jpeg"}'

Response:

< HTTP/1.1 404 Not Found
< content-length: 0

Logs after request:

pm2 logs backend | grep -i "extract_frame:\|get_video_info:"
# (no output - handlers never called)

For comparison, working endpoint:

curl "http://localhost:3000/api/admin/products"
# HTTP 200 OK - returns product list

What I've Tried

1. ✅ Direct .route() chaining (didn't register routes)
2. ✅ web::scope() pattern (scope collision with admin_products)
3. ✅ web::resource() pattern (routes register but don't match)
4. ✅ Different ordering in main.rs (no change)
5. ✅ Full path vs scope+relative path (no change)

Questions for the Community

1. Why does web::resource("/api/admin/products/{id}/video-info") register successfully but not match incoming requests?

2. Is the issue route precedence? Does admin_products::web::scope("/api/admin/products") consume all requests to that path before video_routes resources can match?

3. What's the correct Actix-web pattern for registering dynamic path routes in a separate module that will actually match and route to handlers?

4. Should these routes be added directly to admin_products.rs instead of trying to register them separately?

Additional Context

• All code compiles without errors
• Routes are clearly being registered (logs prove it)
• Other endpoints (not under /api/admin/products) work fine
• The handler code itself is correct (would work if it were called)
• This is blocking further development (need handlers to work to complete feature)

TL;DR: Routes register at startup (confirmed by logs), but don't match incoming requests (404). Handler functions never execute. What's the correct Actix-web pattern for dynamic path routes that will actually match?

[MukundaKatta]

Nine times out of ten this is scope/service ordering — .service(web::scope(...).configure(video_routes)) works, but .configure(video_routes).service(web::scope(...)) doesn't. Also check the path: {id} in actix matches a single segment, so /api/admin/products/42/video-info should hit, but /api/admin/products/42/video-info/ (trailing slash) won't unless you add NormalizePath. A curl of the exact URL you're testing with -v usually pinpoints it.