This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 216837 - Can not log in using Google Chrome
Summary: Can not log in using Google Chrome
Status: VERIFIED FIXED
Alias: None
Product: www
Classification: Unclassified
Component: Admin (show other bugs)
Version: 7.2
Hardware: Macintosh (x86) Mac OS X
: P2 normal (vote)
Assignee: Jan Pirek
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-14 06:43 UTC by driscoll
Modified: 2012-08-21 05:21 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description driscoll 2012-08-14 06:43:19 UTC 
Can not log in via Google Chrome.

To duplicate:  Click on "Log In" in the community issues page.  An empty page appears.  (Actually, the page is powder blue - and the view source shows source - so it's probably a layout problem).

https://netbeans.org/people/login?original_uri=%2Fcommunity%2Findex.html

Works fine in Firefox.
Comment 1 driscoll 2012-08-14 06:46:47 UTC 
Justification for P1:  It almost stopped me from reporting bugs at all.  Provided it's reproducable, has certainly stopped others from reporting bugs.  Reporting bugs on the Netbeans website is probably the second most important feature of the website, after downloading the software itself.
Comment 2 Jan Pirek 2012-08-14 15:57:25 UTC 
Decreasing to P2 as other browsers work.

This is caused by the fact that some of the page properties (some css + js files) on that page are loaded via plain http instead of https like main page content. Chrome considers this as security issue and blocks them and page is then not rendered properly.

I am talking to the team which owns this part of infrastructure, hopefully they will fix it soon.

jan
Comment 3 Jan Pirek 2012-08-14 16:02:05 UTC 
Kenai issue link: http://kenai.com/jira/browse/KENAI-3552
Comment 4 Jan Pirek 2012-08-20 09:37:21 UTC 
this has been just resolved, please verify if you have a chance
Comment 5 driscoll 2012-08-21 05:21:56 UTC 
I verified the fix - all better now!