WebDAV sync issue with Box: msg is not defined
Hello, all.
I suddenly have an error where I can't sync. I don't remember doing anything different.
As of now, I can't sync to Box. The red error icon tells me Webdav verification failed and to verify my file sync settings. When I do that I get the 'msg not defined' error. My box settings and path are correct. I haven't touched them. And I can log into box. I have plenty of space there.
Can someone advise me? I actually have a book due at the end of the month, and I am fact checking all of my inline citations.
Thanks
D526008304
I suddenly have an error where I can't sync. I don't remember doing anything different.
As of now, I can't sync to Box. The red error icon tells me Webdav verification failed and to verify my file sync settings. When I do that I get the 'msg not defined' error. My box settings and path are correct. I haven't touched them. And I can log into box. I have plenty of space there.
Can someone advise me? I actually have a book due at the end of the month, and I am fact checking all of my inline citations.
Thanks
D526008304
This discussion has been closed.
There's a good chance that Box will fix whatever is causing this and it'll go away soon. If you're still seeing this in a few hours, you'll need to contact Box and ask why requests like the one above are failing.
Thanks redcloud111 for placing a customer support ticket.
I recently checked my box and used the diagnosis tool, it failed in "Testing upload to different Box hostnames..." all 5 times.
The Box service claims that the problem has been resolved. Box acknowledges that this was an issue on their end and disrupted far more than Zotero Wevdav.
I see their note that all uploads should be working, but I am still facing the same problem.
Sent the error ref: 1719549115
One thing I've noticed, which I think may be Zotero related is that I'm getting repreated full rapid/fake syncs where it seems to be syncing all my files but really rapidly so it's not actually uploading or downloading anything.
report id. : 321527985
Box has started returning invalid responses for various HTTP errors, including for the 404 error that Zotero triggers as a normal part of the Verify Server process.
Zotero makes a request with
Accept-Encoding: zip, deflate, br
for a nonexistent URL. Box responds with a 404, as it should, but includes theContent-Encoding: gzip
header even though the response is plaintext. This makes it an invalid HTTP response, and it will fail or behave unexpectedly in most HTTP clients.You can see this yourself just by trying to load https://dav.box.com/dav/zotero/nonexistent.prop in Firefox or Chrome. If you get an authentication prompt, just Esc out of it (or enter your credentials) and you'll get an error.
Firefox: Chrome: So they'll need to fix that. If you have an open ticket with Box, you can point them to this comment for the technical explanation of what they need to fix.
(Zotero is showing "msg is not defined" because the invalid response gets interpreted as a failed connection, but normally a connection fails because 1) the server couldn't be reached or 2) there was an SSL certificate/connection problem. The current code doesn't account for a situation where there's a proper SSL connection but the HTTP response is invalid. Since we don't technically need to read the response body for the 404, we can consider putting in a workaround for this, but the server is unequivocally in the wrong here, so a clearer "Invalid response from server" message would also be justified.)
https://status.box.com/
BTW, they have not personally responded to my post yet.
Thanks!
Note that the current beta includes a major overhaul to word processor integration that's still a bit buggy, so if you're using word processor integration and don't want to deal with unexpected issues you're probably better off waiting for either the next stable release of Zotero or for Box to fix this properly on their end.
A recent change to Box means that Box now responds to a request for a non-existent URL with an invalid HTTP response. The header on the 404 now includes
Content-Encoding: gzip
though the response is in plaintext.Because of this mismatch, HTTP clients getting the 404 are failing with Content Encoding Error. You can test this in a browser: https://dav.box.com/dav/nonexistent.prop
The invalid 404 causes certain clients syncing with Box over WebDAV to fail, notably the reference manager Zotero (a major tool for academic research). Zotero is attempting a workaround - see https://forums.zotero.org/discussion/70311/webdav-sync-issue-with-box-msg-is-not-defined .
Nevertheless, Box should not produce an invalid 404 response. Please could this be fixed urgently as it is likely to make other clients behave unexpectedly as well.