To recap:
With USER and PASS defined in ~addons/ide/jhs/config/jhs.ijs,
and those values entered in the login form, the browser
just hangs. (Firefox displays "stopped" in the bottom line.)
I did two hours extensive testing/tracing together with colleague Uwe
Faustmann and another hour peaking at the code and I believe I found
what's wrong.
The corresponding trace through the code is this (caller -> callee):
core.ijs:156: do. r=. 'jev_get_jlogin_ 0'
jlogin.ijs:67: jhr 'jlogin';(css CSS);'';loggedin
utilh.ijs:589: htmlresponse tmpl hrplc 'TITLE ...
utilh.ijs:131/132: putdata LASTRESPONSE=: y
sdclose_jsocket_ SKSERVER
The LASTRESPONSE is the utilh.ijs:html204 noun:
html204=: 0 : 0
HTTP/1.1 204 OK
Content-Type: text/html; charset=utf-8
)
1st observation:
A packet dump on the wire confirms that is emmitted as-is,
i.e. with LFs instead of CRLFs as required by the HTTP standard.
The 3 LFs are the last bytes which get transmitted in either
direction.
2nd observation:
LASTRESPONSE response really is just this header. The html body
(i.e. the "loggedin" page) is completely missing. I wonder what
nukes it off.
At the server side, port 65001 is listening again, but the client is
not asking. My impression is that it awaits further response data from
the server, but none is forthcoming. This would at least correspond to
the status shown: "[transfer] stopped".
I assume that the CRLF standard violation is not really essential here
but the missing body.
Again my question to other beta testers:
Do passwords work for any at all?
This is as close as I am probably able to hunt this down before doing
the other preparations for the trip. (The actual talk; blowing a hole
into our firewall; packing things.) Boarding the train in 18 hours.
Martin
----------------------------------------------------------------------
For information about J forums see http://www.jsoftware.com/forums.htm
