1.0-alpha2 Windows client login problem

Submitted by mkukik on 2010-09-01

I've got login request first time only with "Invalid server response". Then I am unable to enter login details anymore only if I change proxy for example. Tried with or without proxy. Here what Fiddler says:

REQUEST:
POST http://x.x.x.x/webissues1/server/webissues/handler.php HTTP/1.1
Content-Type: multipart/form-data; boundary="nextPart-RUzkSLBzYnS8"
Content-Length: 109
Connection: Keep-Alive
Accept-Encoding: gzip
Accept-Language: en-IE,*
User-Agent: Mozilla/5.0
Host: x.x.x.x

--nextPart-RUzkSLBzYnS8
Content-Disposition: form-data; name="command"

HELLO
--nextPart-RUzkSLBzYnS8--

RESPONSE:
HTTP/1.1 200 OK
Date: Wed, 01 Sep 2010 13:14:49 GMT
Server: Apache/2.2.3 (Red Hat)
X-Powered-By: PHP/5.3.1
X-WebIssues-Version: 1.0-alpha2
Content-Length: 80
Connection: close
Content-Type: text/plain; charset=UTF-8

S 'Xxxxx Webissues Test' '1a1c25f7-59be-4a3d-83dd-20a908fda2d7' '1.0-alpha2'

Thanks,
Martin

I have the same issue. server on linux, client on windows (alpha3).
fresh install from today, after having player a little with 0.x version.

POST http://myhost.com/webissues/server/webissues/handler.php HTTP/1.1
Content-Type: multipart/form-data; boundary="nextPart-wPMAAhqrQCAI"
Content-Length: 109
Connection: Keep-Alive
Accept-Language: en-US,*
User-Agent: Mozilla/5.0 Paros/3.2.13
Host: myhost.com

--nextPart-wPMAAhqrQCAI
Content-Disposition: form-data; name="command"

HELLO
--nextPart-wPMAAhqrQCAI--

which responds with

HTTP/1.1 200 OK
Date: Thu, 30 Dec 2010 06:23:44 GMT
Server: Apache/2.2.3 (CentOS)
X-Powered-By: PHP/5.2.16
X-WebIssues-Version: 1.0-alpha3
Content-Length: 78
Connection: close
Content-Type: text/plain; charset=UTF-8


S 'myhost Webissues' 'e1ea5937-7a14-4196-a67e-1ed3025cc059' '1.0-alpha3'

and the client responds as Invalid rerver response.

any ideas?

It looks like there are some additional characters before the response. Content-Length should be 74 (72 characters + CR + LF) and not 78. Perhaps the utf-8 BOM was prepended for some reason?

Regards,
Michał

Hey Michał
you got it right; it turns out that my Apache was configured with AddDefaultCharset UTF-8
which produced the the extra character. by removing it, it now works fine.
thanks,