-
Notifications
You must be signed in to change notification settings - Fork 62
Known limitations
- gooddata-java issue: DataStoreService call fails with 500
- GoodData internals issue: ONE-851
GoodData WebDAV server unfortunately doesn't follow the specification - section 8.2.3. After receiving the header part of the PUT
request it should send either 100 - continue
or final response (i.e. 401
in case of yet unauthenticated request). Unlikely it sends nothing waiting to receive the request body. The body is sent by gooddata-java with 3s delay implemented in Http client. This has following results.
In case the PUT
on WebDAV is the first request, the client is not yet authenticated. The PUT
with delay causes internal error on WebDAV (status 500
). Unfortunately the InputStream
passed to upload
method is read.
If you met this, please change your code to do some another request first in order to get authenticated properly.
Since the GoodData WebDAV never sends 100 - continue
response, every authenticated request suffers the 3s delay between sending header and body.