Closed GoogleCodeExporter closed 8 years ago
No idea about "line 495 char 3". That's not super helpful. But I did manage to
still
find a system with an old version of IE and I fixed some code in the latest SVN
release. Maybe, you can build that and let me know if it fixes your problem.
Original comment by zod...@gmail.com
on 18 Mar 2009 at 2:28
Still doesn't work, but now doesn't show the javascript error. Now, first it
hangs
on progress bar for a long time, (5 minutes maybe?), then, it displays the
"Connect"
button (without ever having shown the login prompt), when clicked, nothing
happens
and there is still a connect error. I'll pursue this within the next week at
some
point and try to figure out how to work IE Ajax debugging.
Original comment by TomOeh...@gmail.com
on 18 Mar 2009 at 6:44
I just submitted a new version, which should have more work-arounds for IE6, and
which allows binding to low ports.
In general, IE6 seems to erroneously cache POST requests every once in a while.
That's quite bad. We try to persuade it not to do this, but I am not sure we
catch
all cases, yet.
So, more testing would be appreciated. It works with the copy of IE6 that I
have, but
there could very well be different versions out there.
Original comment by zod...@gmail.com
on 18 Mar 2009 at 7:20
OK... so... HERE IS THE DEAL with this now... A clean IE6 on Windows 2000 under
VmWare now works. From my work computer, which has IE6 on Windows XP, it still
hangs
when going out the corporate firewall to a shellinaboxd on 443. From my work
computer, running IE6 on Windows XP, out the corporate firewall ***through the
Apache
proxy***, it works fine... so... SOMETHING about the shellinaboxd handles https
is
_still broken_ *some* IE6 installations or some kinds of connections. Note, it
is
weird- when I accidentally typed a path, I got the "file not found", when I
right-click, I get the menu... but it doesn't give the login prompt. When I
turn on
-d, I don't see any posts.
BUT... the upshot of my personal situation is that since I'm proxying through
apache
with apache listening SSL and sib running -t now, and as it works that way, it
isn't
a priority anymore for me. I'm glad to help out since I can reproduce the
issue, but
am not sure I'll have the time in the next week to turn on ssldump and trace the
traffic, and it is problematic for me to try it over http, as http on my one
static
ip maps to another webserver, but I'll try that at some point. I only know it
fails
over https, the next test is to have it listen on 80 and change the port
forwarding
at the router.
Original comment by TomOeh...@gmail.com
on 19 Mar 2009 at 11:23
This very much looks like a problem with IE6 caching POST responses, which we
expect
to go uncached. I added explicit no-cache headers in the most recent SVN
release. Can
you test if that fixes the problem?
Original comment by zod...@gmail.com
on 19 Mar 2009 at 10:19
My testing suggests that the IE6 (and IE5.5) problems should all be fixed with
version 2.5 of ShellInABox. Please reopen this issue, if the problem persists,
or
create a new issue if you discover other IE related problems.
Original comment by zod...@gmail.com
on 21 Mar 2009 at 4:22
Original issue reported on code.google.com by
TomOeh...@gmail.com
on 17 Mar 2009 at 4:02