Opened 11 years ago
Closed 11 years ago
#10130 closed bug (fixed)
HaikuLauncher/Webkit issue when logging into webmailcluster.perfora.net (1und1 webmail)
Reported by: | ronald-scheckelhoff-trac | Owned by: | pulkomandy |
---|---|---|---|
Priority: | normal | Milestone: | R1 |
Component: | Applications/WebPositive | Version: | R1/Development |
Keywords: | HaikuLauncher/Webkit | Cc: | |
Blocked By: | Blocking: | ||
Platform: | x86 |
Description
Haiku revision: Nightly image h46279
Application: Haiku-launcher package and Webkit, as downloaded from pulkomandy's blog link: http://www.haiku-os.org/blog/pulkomandy/2013-10-18_webkit_weekly_report_4
When visiting webmailcluster.perfora.net, and trying to execute the login page, HaikuLauncher stops and dispatches the following error:
MESSAGE https://email.1and1.com/ox6/ox.html#session=b3fe7103c8414b90a5320205b27b3d8e&store=true:28 ReferenceError: Can't find variable: initAll
The last portion of the log output was captured to a file. See attached file (haiku_launcher_log_output.txt)
Attachments (1)
Change History (8)
by , 11 years ago
Attachment: | haiku_launcher_log_output.txt added |
---|
follow-up: 2 comment:1 by , 11 years ago
Component: | Applications → Applications/WebPositive |
---|---|
Owner: | changed from | to
Status: | new → assigned |
comment:2 by , 11 years ago
comment:3 by , 11 years ago
Hi, From a quick look at the log, the first and most obvious problem is that the website sends gzipped javascript code. We don't have support for compressed HTTP yet, so this won't work.
Ideally the web server should detect that we can't handle that and unpack the data itself, but I'll be adding the feature to our network code anyway, as it makes everything download faster.
comment:4 by , 11 years ago
Sounds like it'll be an easy fix, when the overall compression scheme is added eventually. Thanks!
comment:7 by , 11 years ago
Resolution: | → fixed |
---|---|
Status: | assigned → closed |
It may not be fair to expect the developers to track this one down. I don't think 1and1.com has a free account offering, and it would probably require a login to step through the app in order to pinpoint the problem. Am I correct? So, maybe this is just an FYI ticket for future reference (until a point when maybe I can debug it with my own account eventually)