BB sends a HEAD request like this:
HEAD /SELoginAccess.jsp HTTP/1.0
User-Agent: BigBrother/1.9c
Host: myhost.mydomain.com:8068
Hobbit sends a GET request like this:
GET /SELoginAccess.jsp HTTP/1.1
Connection: close
Host: myhost.mydomain.com
User-Agent: Hobbit bbtest-net/4.2.0
Accept: */*
Pragma: no-cache
which should be much more like a "normal" browser request. I dont think
the HTTP 1.0/1.1 difference matters, but you *can* ask Hobbit to use
HTTP 1.0 by defining the URL with "http10" as in
1.2.3.4 myhost # http10://myhost/SELoginAccess.jsp
The only other difference is that BB includes the port number in the
"Host:" header. I haven't noticed that before. I've just checked the
HTTP 1.1 RFC, and it's true that the "Host" header must include the port
number if it is not the default (80 for http, 443 for https). You may
want to try the attached patch to see if it makes a difference.