Can not verify server: error message -8

FrankBase
(Windows XP/Ff 3.0.1/Zotero 1.5-sync2.1)

Syncing with the Zotero Sync Server works fine, but I can not sync with the https:// university server.
Verify Server gives error message -8 .
Does anyone know what this means?

I can load the URL in Firefox, and Ff seems to accept the certificate.




Thanks for your advice,

Frank
  • dstillman
    Error -8 indicates that the server is rejecting one of the HTTP requests as invalid.

    Can you run Firefox with debug output enabled and send the debug output for the Verify Server attempt to support@zot....org? Thanks.
  • dstillman
    Thanks for sending the debug output. I've fixed various problems with WebDAV on Microsoft IIS 5.1 servers (including the error you were seeing) in the latest trunk build. Your host uses IIS 6, which I don't currently have access to, but the storage code should generally be more open-minded now in terms of the server responses it receives.
  • FrankBase
    Thanks for your comments,

    I installed the trunk XPI and now I'm running Zotero version 1.5a1.r3395 .
    However - I still can not sync, and I'm still getting error message -8 .

    FYI I will send you the debug output again.

    best,
    Frank
  • dstillman
    Sorry, I forgot that our automated XPI build script is currently broken. Revision 3401 should now be available. Try again.
  • FrankBase
    Hi Dan,

    It works!
    With revision 3405 I was able to sync the PDF attachments.
    At present I'm running r3435, and still encountering some problems (slow starting of FF, and errors like "last error: download request already exists in zotero.sync.storage.addRequest()" and "last error: Conflict! Last known mod time does not match remote time!"), but I'll follow the other discussions for these topics.

    Thanks for your help.
    Best, Frank
  • Resting stage
    I am having the same -8 error when I want to verify my server. I am using Firefox 3.0.11 on Ubuntu 9.04. My webDAV host works perfectly fine for other applications. This is the debug info:

    zotero(3): HTTP OPTIONS for https://username:password@www.mydrive.ch/zotero/

    zotero(3): ===>400<===(number)

    zotero(3): Date: Mon, 13 Jul 2009 16:07:53 GMT
    Server: Apache/2.2.9 (Debian)
    Set-Cookie: _mydrive_session=dd394d6459caaa745f050a7a94f76b2e; path=/; domain=.mydrive.ch
    Expires: Thu, 19 Nov 1981 08:52:00 GMT
    Cache-Control: private
    Pragma: cache
    Vary: Accept-Encoding
    Content-Encoding: gzip
    Content-Length: 43
    Connection: close
    Content-Type: text/html; charset=utf-8


    zotero(3): <h1>400 Bad Request</h1>

    zotero(3): ===>400<===(number)


    Many thanks in advance!
  • dstillman
    Resting stage: I'm not sure what other applications you're referring to, but HTTP OPTIONS is the standard way of determining whether a server supports WebDAV. Transmit on OS X uses it, OS X's built-in WebDAV support uses it, and even cadaver, the official webdav.org client, uses it. Granted, I don't know what these clients do if the server returns a 400 Bad Request response to the OPTIONS request (feel free to test your server with cadaver), but it seems like a reasonable requirement.

    You might want to try manually creating the 'zotero' folder to see if the server still returns a 400. You can also try enabling extensions.zotero.sync.storage.verified in about:config to bypass the verification step, though an OPTIONS request is used in one other part of the code as well, which could be a problem for you.
Sign In or Register to comment.