Update CADDY.md documentation to reflect corrected Caddyfile configuration and optimizations
This commit is contained in:
13
CADDY.md
13
CADDY.md
@@ -9,7 +9,7 @@ The Caddy configuration is defined in the [Caddyfile](Caddyfile) and includes:
|
||||
1. Automatic SSL certificate management with Let's Encrypt
|
||||
2. Reverse proxy to the Flask application
|
||||
3. Proper WebSocket support for real-time updates
|
||||
4. Proxy header forwarding for client IP and protocol information
|
||||
4. Simplified configuration with automatic header forwarding
|
||||
|
||||
## Setup Instructions
|
||||
|
||||
@@ -33,7 +33,7 @@ The Caddy configuration is defined in the [Caddyfile](Caddyfile) and includes:
|
||||
- Caddy automatically obtains and renews SSL certificates from Let's Encrypt
|
||||
- All HTTP traffic is automatically redirected to HTTPS
|
||||
- WebSocket connections are properly handled and forwarded to the Flask-SocketIO application
|
||||
- Proxy headers are forwarded to preserve client IP and protocol information
|
||||
- Caddy automatically forwards standard proxy headers to preserve client IP and protocol information
|
||||
|
||||
## WebSocket Support
|
||||
|
||||
@@ -46,4 +46,11 @@ The configuration includes specific handling for WebSocket upgrade requests to e
|
||||
}
|
||||
```
|
||||
|
||||
This ensures that SocketIO connections can be established and maintained properly through the proxy.
|
||||
This ensures that SocketIO connections can be established and maintained properly through the proxy.
|
||||
|
||||
## Configuration Optimization
|
||||
|
||||
The Caddyfile has been optimized to:
|
||||
- Remove unnecessary header forwarding directives (Caddy automatically forwards standard headers)
|
||||
- Maintain clear separation between general reverse proxy rules and WebSocket-specific rules
|
||||
- Keep the configuration simple and maintainable
|
Reference in New Issue
Block a user