cdn-rs

A simple CDN server written in Rust, using axum and redb. Supports user authentication, file/image upload, and automatic cleanup of inactive users.

Getting Started

1. Build and run:

   cargo run --release
   

   The server will listen on 0.0.0.0:3000 (or your configured port).

2. Authentication:

   • All upload routes require a JWT token in the Authorization: Bearer <token> header.
   • Register and login to get a token.

Routes

1. Register

• POST /auth/register
• Body (JSON):

  {
    "username": "yourname",
    "password": "yourpassword"
  }
  

• Response (201):

  {
    "token": "<jwt>",
    "user_id": "<uuid>",
    "username": "yourname"
  }
  

2. Login

• POST /auth/login
• Body (JSON):

  {
    "username": "yourname",
    "password": "yourpassword"
  }
  

• Response (200):

  {
    "token": "<jwt>",
    "user_id": "<uuid>",
    "username": "yourname"
  }
  

3. Get Current User

• GET /me
• Headers:
  • Authorization: Bearer <token>
• Response (200):

  {
    "id": "<uuid>",
    "username": "yourname",
    "created_at": "<timestamp>",
    "last_activity": "<timestamp>"
  }
  

4. Upload File/Image

• POST /upload
• Headers:
  • Authorization: Bearer <token>
• Body:
  • multipart/form-data with a field named file containing the file to upload.
• Response (201):

  File uploaded successfully. ID: <uuid>
  Access at: /files/<uuid> or /images/<uuid>
  

5. Download File

• GET /files/:id
• Response (200):
  • Raw file bytes, with Content-Type set to the original MIME type.

6. Download Image (Full)

• GET /images/:id
• Response (200):
  • Raw image bytes, with Content-Type set to the original MIME type.

7. Download Image Variant

• GET /images/:id/:variant
  • :variant must be one of thumb, mid, or full.
• Response (200):
  • Raw image bytes, with Content-Type set to the original MIME type.

8. List Files/Images

• GET /list
• Response (200):

  {
    "files": ["<uuid>", ...],
    "images": ["<uuid>", ...],
    "total": 42
  }
  

9. List Sessions/Tokens

• POST /auth/tokens
• Body (JSON):

  {
    "username": "yourname",
    "password": "yourpassword"
  }
  

• Response (200):

  [
    {
      "token": "<jwt>",
      "last_used": "<timestamp>"
    },
    // ...
  ]
  

10. Invalidate Session/Token

• POST /auth/invalidate
• Body (JSON):

  {
    "username": "yourname",
    "password": "yourpassword",
    "token": "<jwt>"
  }
  

• Response (200):

  Token invalidated
  

Error Responses

• 400 Bad Request: Invalid input or missing fields.
• 401 Unauthorized: Missing or invalid JWT token.
• 404 Not Found: Resource not found.
• 500 Internal Server Error: Unexpected server error.

Notes

• Images are stored in three qualities: thumb (150px), mid (800px), full (original).
• All files are compressed with gzip before storage.
• Inactive users (>1 year) have their files purged automatically.
• You can list all active tokens/sessions for your account and see when each was last used.
• You can invalidate (delete) any session/token by providing your username, password, and the token.