feat: detect CORS errors and show actionable guidance on login
Distinguish CORS-blocked requests from genuine network failures using a no-cors probe, so users deploying via Docker see a specific message pointing to their JMAP server's CORS settings instead of a misleading "unable to reach the server" error.
This commit is contained in:
+1
-1
@@ -22,6 +22,7 @@ This document tracks the development status and planned features for JMAP Webmai
|
||||
### JMAP Server Connection
|
||||
- [x] Session establishment and keep-alive
|
||||
- [x] Connection error handling and retries
|
||||
- [x] CORS error detection with actionable user guidance
|
||||
- [x] Storage quota display
|
||||
- [x] Server capability detection
|
||||
- [x] Shared folders support (multi-account access)
|
||||
@@ -250,7 +251,6 @@ This document tracks the development status and planned features for JMAP Webmai
|
||||
|
||||
### Security Enhancements
|
||||
- [ ] Rate limiting
|
||||
- [ ] CORS configuration
|
||||
|
||||
## Known Issues
|
||||
|
||||
|
||||
Reference in New Issue
Block a user