glassfish
  1. glassfish
  2. GLASSFISH-16308

Admin console not loading on Safari after enabling secure-admin

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Cannot Reproduce
    • Affects Version/s: 3.1
    • Fix Version/s: None
    • Component/s: admin
    • Labels:
      None
    • Environment:

      Server: FreeBSD 8.2 x64
      Client: Mac OS X 10.6.7

      Description

      • Download and install Glassfish 3.1 final (b43)
      • asadmin start-domain
      • asadmin enable-secure-admin
      • asadmin stop-domain
      • asadmin start-domain
      • open Safari web-browser and try to connect to the admin console via https on port 4848

      Result: the admin console GUI won't load: error 404: "Failed to open page"

      The result is the same whether you use Glassfish's own self-signed certificate or if you use an authority signed certificate.

      On Firefox everything works perfectly. It connects to the admin console GUI just fine.

      No error or exception can be found in server.log.

        Activity

        Hide
        nabizamani added a comment - - edited

        I can reproduce this issue with Safari 5.1.2 on OS X Lion + Glassfish 3.1.1.
        I also have no problems with Firefox and no Problem with Chrom! Only Safari makes problems!
        But I am also sure that before my Safari Update everything worked just fine - so in other words: this seems to be a Safari issue!!!
        Anyway, we need a solution for that. Maybe you could investigate...

        Please reopen this issue!

        ps
        see here for example: https://discussions.apple.com/thread/3192257?start=0&tstart=0

        Show
        nabizamani added a comment - - edited I can reproduce this issue with Safari 5.1.2 on OS X Lion + Glassfish 3.1.1. I also have no problems with Firefox and no Problem with Chrom! Only Safari makes problems! But I am also sure that before my Safari Update everything worked just fine - so in other words: this seems to be a Safari issue!!! Anyway, we need a solution for that. Maybe you could investigate... Please reopen this issue! ps see here for example: https://discussions.apple.com/thread/3192257?start=0&tstart=0
        Hide
        buddypine added a comment -

        Same issue here with Safari 5.1.7 and Glassfish 3.1.2

        Show
        buddypine added a comment - Same issue here with Safari 5.1.7 and Glassfish 3.1.2
        Hide
        norasodan added a comment -

        I can reproduce with Safari 5.1.7 on OSX Lion and Glassfish 3.1.2 b23.

        Please reopen this issue!

        Show
        norasodan added a comment - I can reproduce with Safari 5.1.7 on OSX Lion and Glassfish 3.1.2 b23. Please reopen this issue!
        Hide
        rherschke added a comment -

        also the problem here:
        Glassfish 3.1.2 b23
        Safari 5.1.7 (7534.57.2)
        OS X Lion 10.7.4

        worked with Safari pre 5.0 versions.

        Please reopen this issue and please don't assume to start a browser nor an OS-war on this issue!

        Show
        rherschke added a comment - also the problem here: Glassfish 3.1.2 b23 Safari 5.1.7 (7534.57.2) OS X Lion 10.7.4 worked with Safari pre 5.0 versions. Please reopen this issue and please don't assume to start a browser nor an OS-war on this issue!
        Hide
        Tim Quinn added a comment -

        I have just retried this with the same setup which rherschke described. Naturally, it works fine for me.

        I was able to get something close - but not exactly the same - as the failure people are describing here by doing the following:

        1. I was connected to Oracle's internal network using VPN; Safari was open and I had visited various sites.
        2. I installed GlassFish 3.1.2 b23.
        3. asadmin start-domain
        4. asadmin change-admin-password (this is required or GlassFish rejects the next step).
        5. asadmin enable-secure-admin
        6. asadmin stop-domain
        7. asadmin start-domain
        8. Use Safari to connect to https://localhost:4848. Worked.
        9. Use Safari to connect to https://192.168.2.102:4848. Worked.
        10. Use Safari to connect to https://host-assigned-by-vpn:4848. Worked.

        11. Disconnect from VPN. I did not restart GlassFish or Safari.
        12. Use Safari to connect to https://192.168.2.102:4848. Worked.
        13. Run uname -n to get the current host name.
        14. Use Safari to connect to https://output-from-uname-minus-n:4848. It took a VERY long time but it eventually worked.
        15. Restart Safari.
        16. Repeat 14. Worked immediately.

        I have auto-proxy discovery set in networking.

        I believe it is well-known (if not well-loved) behavior of Safari that going on or off VPN causes delays like what I described in step 14, and I have seen this trying to connect to other web sites. Restarting Safari clears that up.

        I can believe that, depending on exactly what goes on inside Safari and the network stack during step 14, I might have received a timeout instead of a slow response if it took a little longer.

        Those of you who have seen this problem: Could there be something related to networking on your Macs that might be contributing to this? Going on or off VPN, or moving from one network to another?

        Please report what sort of name you are specifying for the host. We don't need to know the exact name; it just might help to know whether you are using numerical addresses, whether they are 192.168.x.y or "real" numeric addresses, "localhost," some other host name. Also please check your /etc/hosts file.

        Show
        Tim Quinn added a comment - I have just retried this with the same setup which rherschke described. Naturally, it works fine for me. I was able to get something close - but not exactly the same - as the failure people are describing here by doing the following: 1. I was connected to Oracle's internal network using VPN; Safari was open and I had visited various sites. 2. I installed GlassFish 3.1.2 b23. 3. asadmin start-domain 4. asadmin change-admin-password (this is required or GlassFish rejects the next step). 5. asadmin enable-secure-admin 6. asadmin stop-domain 7. asadmin start-domain 8. Use Safari to connect to https://localhost:4848 . Worked. 9. Use Safari to connect to https://192.168.2.102:4848 . Worked. 10. Use Safari to connect to https://host-assigned-by-vpn:4848 . Worked. 11. Disconnect from VPN. I did not restart GlassFish or Safari. 12. Use Safari to connect to https://192.168.2.102:4848 . Worked. 13. Run uname -n to get the current host name. 14. Use Safari to connect to https://output-from-uname-minus-n:4848 . It took a VERY long time but it eventually worked. 15. Restart Safari. 16. Repeat 14. Worked immediately. I have auto-proxy discovery set in networking. I believe it is well-known (if not well-loved) behavior of Safari that going on or off VPN causes delays like what I described in step 14, and I have seen this trying to connect to other web sites. Restarting Safari clears that up. I can believe that, depending on exactly what goes on inside Safari and the network stack during step 14, I might have received a timeout instead of a slow response if it took a little longer. Those of you who have seen this problem: Could there be something related to networking on your Macs that might be contributing to this? Going on or off VPN, or moving from one network to another? Please report what sort of name you are specifying for the host. We don't need to know the exact name; it just might help to know whether you are using numerical addresses, whether they are 192.168.x.y or "real" numeric addresses, "localhost," some other host name. Also please check your /etc/hosts file.

          People

          • Assignee:
            Tim Quinn
            Reporter:
            ref
          • Votes:
            0 Vote for this issue
            Watchers:
            4 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Time Tracking

              Estimated:
              Original Estimate - 2 hours
              2h
              Remaining:
              Remaining Estimate - 2 hours
              2h
              Logged:
              Time Spent - Not Specified
              Not Specified