more than one server active seems to trigger a bug where the second server fails
while testing something, we noticed that when more than one server is active, accessing the shares of one and then switching to the other makes things not work.
it would appear as if the first GET /shares was to be cached, so switching to the other server does not seem to issue a GET /shares API call.
the app crashes, which seems like a second bug -- a 404 should not crash the app.
#10 Updated by cpg about 7 years ago
- Priority changed from Medium to Normal
this appears to work well. tested with remote access via the proxy, with multiple servers.
we will not merge this to master yet. not until we have a chance to release the origin server with Very: Session in it.
releasing without the origin support for Vary: Session will lead to confused users and also possibly worried users that their data could be corrupted.
i will keep it on feedback until we have released the origin server with this support.
Also available in: Atom