Changes to ticket 8a7a49c47d

By drh on 2009-08-01 13:44:36. See also: artifact content, and ticket history

1. Appended to comment:

   ---

   drh added on 2009-08-01 13:44:36:
   The error was occurring prior to parsing the HTTP request header and so the server did not know that it was dealing with sync protocol - it figured the request was an ordinary HTTP/HTML browser request. So it generates an HTML error message. The fix is to modify the client to detect HTML error messages and try to do something reasonable with them.

   See check-in 80457ec79be10b32f372c69e0093c8fea7f0471b.

2. Change resolution to "Fixed"
3. Change status to "Fixed"