Bug #14383
closed
- Status changed from New to In Progress
- Subject changed from Java SDK double slash to Java SDK double slash bug with arvados-controller
- Description updated (diff)
- Status changed from In Progress to New
- Subject changed from Java SDK double slash bug with arvados-controller to [API] Java SDK double slash bug with arvados-controller
Actually, the correct fix is to fix the server so that it isn't breaking existing clients.
- Target version set to 2018-11-14 Sprint
- Related to Story #13497: [API] Initial "arvados-controller" server that proxies API endpoints to Rails server added
- Assigned To set to Tom Morris
- Target version changed from 2018-11-14 Sprint to 2018-11-28 Sprint
Tom Morris wrote:
Actually, the correct fix is to fix the server so that it isn't breaking existing clients.
Continuing to tolerate client bugs that were tolerated before should be easy enough here. But the buggy client should still be fixed. API endpoints are "/arvados/...", not "//arvados/...".
- Target version changed from 2018-11-28 Sprint to 2018-12-12 Sprint
- Release deleted (
14)
- Target version changed from 2018-12-12 Sprint to 2018-12-21 Sprint
Tom Clegg wrote:
I wonder why f0d62ea064d32b980f723e37972788cbd693c2ff didn't fix this. Merged Fri Jul 13 2018.
That "fix path transparently" bit doesn't apply to GET reqs, because following a 301 redirect doesn't change the request method. If a client simply can't handle redirects, even GET requests fail.
I think it's OK to say clients need to be able to follow 301 redirects -- especially clients that aren't paying attention to the paths specified in the discovery doc.
The best fix would be to make Java SDK follow redirects, and fix that broken path to avoid the extra request.
- Target version changed from 2018-12-21 Sprint to 2019-01-16 Sprint
- Target version changed from 2019-01-16 Sprint to 2019-01-30 Sprint
- Status changed from New to In Progress
- Target version changed from 2019-01-30 Sprint to 2019-02-13 Sprint
- Target version changed from 2019-02-13 Sprint to 2019-02-27 Sprint
- Status changed from In Progress to Resolved
Also available in: Atom
PDF