Bug 80033 - SWT Browser does not display https.
Summary: SWT Browser does not display https.
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: SWT (show other bugs)
Version: 3.1   Edit
Hardware: PC Linux
: P3 normal with 11 votes (vote)
Target Milestone: 3.2.1   Edit
Assignee: Grant Gayed CLA
QA Contact:
URL:
Whiteboard:
Keywords:
: 85661 133645 (view as bug list)
Depends on: 132500
Blocks: 99697
  Show dependency tree
 
Reported: 2004-12-02 11:49 EST by Jeff Pound CLA
Modified: 2006-08-30 16:15 EDT (History)
18 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jeff Pound CLA 2004-12-02 11:49:52 EST
Ive tried this with 2 different configurations on linux/gtk. Both of them will
load http sites just fine but neither of them will load https sites.

eclipse 3.1M3
Mozilla 1.4
IBM jvm 1.4.2

eclipse 3.1M3
Mozilla 1.7
SUN jvm 1.4.2
Comment 1 Ron Capelli CLA 2004-12-10 16:24:24 EST
The SWT Browser doesn't set up a Mozilla profile, so the default is under the
Mozilla install directory (e.g., /usr/lib/mozilla).  When navigating to a site
using https, Mozilla writes various files in the profile (key3.db, cert8.db, and
secmod.db).  For a non-root user, the profile directory is read-only, so this fails.

As root, https may work.  If not, there may be yet something else missing to
support https.
Comment 2 Jeff Pound CLA 2004-12-13 11:46:52 EST
Ron, I tried running eclipse as root and https still doesnt work :(  I'm going
to try to have a look at this if i have time this week though im not familiar
with the swt browser widget code base.  If you have any suggestions as to where
the problem may be im all ears :)
Comment 3 Christophe Cornu CLA 2005-02-03 16:37:58 EST
fixed v>20050203

It is now possible to use the SWT Browser with the HTTPS Eclipse bugzilla (I'm
closing this very PR through the SWT Browser). Support is minimal - preferences,
passwords are not persisted after the application exits etc. but that's a start.
bug 83420 captures related feature requests.

Thanks to Darin Fisher, Javier Pedemonte from Mozilla and other IBMers (Ron
Capelli) for discussions and feedback on the different ways support can be
added. Further HTTPS issues will be opened in separate PRs.
Comment 4 Christophe Cornu CLA 2005-02-17 22:59:19 EST
Reopened. M5 testing shows the profile support as currently implemented is
causing  crashes bug 85662. HTTPS support is disabled as a result until a better
implementation can be provided.
Comment 5 Christophe Cornu CLA 2005-04-19 18:04:24 EDT
*** Bug 85661 has been marked as a duplicate of this bug. ***
Comment 6 Michael Champion CLA 2006-03-14 13:47:23 EST
Is there any plans to address this in 3.2?

Currently I'm seeing this issue on RH EL3 with Mozilla 1.7.10. Using HTTPS fails (should prompt about a mismatched SSL cert). The browser just displays a completely blank page without any obvious error. All works fine for HTTP (or HTTPS on Windows with IE). I've run it as root with the same behavior.

Any suggestions for a workaround?
Comment 7 Grant Gayed CLA 2006-03-14 13:56:05 EST
It is planned to revisit this for 3.2.  There aren't any suggested workarounds at this point.
Comment 8 Grant Gayed CLA 2006-03-17 16:01:02 EST
I've verified that cloning an initial profile as opposed to creating a new one still results in lots of eclipse crashes, so it still looks like a way is needed to display https without using a profile at all.
Comment 9 Steve Northover CLA 2006-05-10 15:18:46 EDT
We are investigating bug 132500 which requires a profile.  Fixing that bug would, we believe, fix this one as well.
Comment 10 Steven Wasleski CLA 2006-05-18 12:24:21 EDT
It appears a fix for bug 132500 has been found but that it will not appear until 3.2.1 or 3.3.  Has anyone been able to confirm if that changes also fixes this bug?
Comment 11 Grant Gayed CLA 2006-05-18 12:37:15 EDT
It does, and also bug 91348.
Comment 12 Grant Gayed CLA 2006-06-23 10:11:31 EDT
Fixed > 0623 in HEAD on linux-gtk, linux-gtk-64 and linux-motif.  Note that since this is fixed as a side effect of the fix for bug 132500, this fix will likely appear in 3.2.1 as well, so marking the target milestone accordingly.
Comment 13 Mik Kersten CLA 2006-06-23 11:40:42 EDT
Excellent!  For Linux users this was killing Mylar's browser integration for repositories that like https (e.g. Bugzilla and Trac).
Comment 14 Mik Kersten CLA 2006-06-23 11:51:48 EDT
*** Bug 133645 has been marked as a duplicate of this bug. ***
Comment 15 Grant Gayed CLA 2006-06-26 15:50:36 EDT
FYI: This functionality will likely be disabled in tomorrow's integration build because it has been causing the unit tests of some other plugins to fail (unless a fix can be found quickly).
Comment 16 Grant Gayed CLA 2006-07-07 16:43:02 EDT
To update, an updated fix for this has been released to HEAD, so it should appear in the next integration build.
Comment 17 Grant Gayed CLA 2006-07-26 13:45:24 EDT
this fix has been added to the 3.2.1 stream
Comment 18 Ian He CLA 2006-08-30 16:14:30 EDT
I retested with the latest AST driver (contains the fix of 80033). I still don't see the https get displayed. When I try to bring up admin console from AST server view, I got a meaasge window:

8/30/06 16:00:51:426 EDT] 0000002e SSLHandshakeE E   SSLC0008E: Unable to initialize SSL connection.  Unauthorized access was denied or security settings have expired.  Exception is javax.net.ssl.SSLException: javax.net.ssl.SSLHandshakeException: Received fatal alert: bad_certificate.

The internal browser does not show.

If I configure to use the external browser, it works fine.