<link> - "rel='shortcut icon'" Not Working with HTTPS???

Collapse
This topic is closed.
X
X
 
  • Time
  • Show
Clear All
new posts
  • Todd Peterson

    <link> - "rel='shortcut icon'" Not Working with HTTPS???

    I'm encountering some wierd behavior with a <link> tag over an HTTPS
    connection, vs. an HTTP connection...

    In an ASP/HTML page on my website, I've add a <link rel="shortcut
    icon"...> in order to allow the users to add a shortcut (with icon) on
    their desktop, as well as seeing the icon in the URL. Our development
    server allows both HTTP and HTTPS connections, but the icon only
    appears to be available when requesting the page via HTTP???

    When I hit the page from a browser as http://myweb/mypage.asp, I can
    send a shortcut to my desktop and the Icon is associated with that
    shortcut as well as the URL in the address bar showing the Icon, much
    like a yahoo icon in the URL.

    When I hit the page from a browser as https://myweb/mypage.asp, and
    send the shortcut to the desktop, I get a default IE Icon and same
    goes for the URL... When I do a "view source", the <link> line is
    present, so I'm at a loss as to why it is not working

    Any help would be greatly appreciated! Below is an example of the
    code in the page:

    <HTML>
    <HEAD>
    <META NAME="GENERATOR " Content="Micros oft Visual Studio 6.0">
    <link rel="shortcut icon" href="myLogo.ic o" type="image/x-icon">
    </HEAD>
    <BODY>

    <P>&nbsp;</P>

    </BODY>
    </HTML>
  • Klaus Johannes Rusch

    #2
    Re: &lt;link&gt; - &quot;rel='shor tcut icon'&quot; Not Working with HTTPS???

    Todd Peterson wrote:
    [color=blue]
    > I'm encountering some wierd behavior with a <link> tag over an HTTPS
    > connection, vs. an HTTP connection...
    >
    > <link rel="shortcut icon" href="myLogo.ic o" type="image/x-icon">
    >[/color]

    <link rel="shortcut icon" href="http://www.example.com/myLogo.ico"
    type="image/x-icon"> should work

    --
    Klaus Johannes Rusch
    KlausRusch@atme dia.net



    Comment

    • Todd Peterson

      #3
      Re: &lt;link&gt; - &quot;rel='shor tcut icon'&quot; Not Working with HTTPS???

      Thanks guys! I appreciate the responses!

      Best Regards,
      Todd


      "D. Stussy" <kd6lvw@bde-arc.ampr.org> wrote in message news:<Pine.LNX. 4.56.0308150051 420.133@kd6lvw. ampr.org>...[color=blue]
      > On Thu, 14 Aug 2003, Klaus Johannes Rusch wrote:[color=green]
      > > Todd Peterson wrote:[color=darkred]
      > > > I'm encountering some wierd behavior with a <link> tag over an HTTPS
      > > > connection, vs. an HTTP connection...
      > > >
      > > > <link rel="shortcut icon" href="myLogo.ic o" type="image/x-icon">
      > > >[/color]
      > >
      > > <link rel="shortcut icon" href="http://www.example.com/myLogo.ico"
      > > type="image/x-icon"> should work[/color]
      >
      > Also note that for some web servers, HTTP and HTTPS protocols for fetching
      > things have different document roots. You may have to duplicate your icons
      > into the HTTPS document root (if you don't want to do the above).[/color]

      Comment

      • Todd Peterson

        #4
        Re: &lt;link&gt; - &quot;rel='shor tcut icon'&quot; Not Working with HTTPS???

        Ok... so I was able to give the recommendation a shot and for some
        reason, it still isn't working???

        We are running IIS and as far as I know, there is only one document
        root "inetpub\wwwroo t\myapp". I was preferring not to use the
        absolute path, "http://myserver...", in the link reference as the URL
        is different for our development, test and production environments.
        In the interest of just getting it to work, I coded in the absolute
        path to my production server and made sure to put the .ico file in an
        "images" directory so that it would work for dev, test and prod, only
        pointing to the production file for each instance. i.e.
        "http://ProductionServe r/MyApp/images/myIcon.ico"

        <I hope I haven't completely caused eyes to glaze over> ;-)

        Again, to my dismay... the icon was picked up when accessing the page
        via HTTP and missing when accessing via HTTPS?

        Is there something else I'm missing? I'm truly perplexed that upon
        doing a "view source" of the HTTPS page, I see the <link> with the
        appropriate location yet it doesn't seem to get delivered to the
        browser

        Thanks again for any suggestions!

        Best Regards,
        Todd

        "D. Stussy" <kd6lvw@bde-arc.ampr.org> wrote in message news:<Pine.LNX. 4.56.0308150051 420.133@kd6lvw. ampr.org>...[color=blue]
        > On Thu, 14 Aug 2003, Klaus Johannes Rusch wrote:[color=green]
        > > Todd Peterson wrote:[color=darkred]
        > > > I'm encountering some wierd behavior with a <link> tag over an HTTPS
        > > > connection, vs. an HTTP connection...
        > > >
        > > > <link rel="shortcut icon" href="myLogo.ic o" type="image/x-icon">
        > > >[/color]
        > >
        > > <link rel="shortcut icon" href="http://www.example.com/myLogo.ico"
        > > type="image/x-icon"> should work[/color]
        >
        > Also note that for some web servers, HTTP and HTTPS protocols for fetching
        > things have different document roots. You may have to duplicate your icons
        > into the HTTPS document root (if you don't want to do the above).[/color]

        Comment

        • Daniel R. Tobias

          #5
          Re: &lt;link&gt; - &quot;rel='shor tcut icon'&quot; Not Working with HTTPS???

          Todd Peterson wrote:[color=blue]
          > Is there something else I'm missing? I'm truly perplexed that upon
          > doing a "view source" of the HTTPS page, I see the <link> with the
          > appropriate location yet it doesn't seem to get delivered to the
          > browser[/color]

          It might be helpful to supply an actual URL so people can try to debug it.

          --
          == Dan ==
          Dan's Mail Format Site: http://mailformat.dan.info/
          Dan's Web Tips: http://webtips.dan.info/
          Dan's Domain Site: http://domains.dan.info/

          Comment

          • Tim

            #6
            Re: &lt;link&gt; - &quot;rel='shor tcut icon'&quot; Not Working with HTTPS???

            On 15 Aug 2003 15:49:31 -0700,
            todd_peterson@b illing.com (Todd Peterson) wrote:
            [color=blue]
            > We are running IIS and as far as I know, there is only one document
            > root "inetpub\wwwroo t\myapp". I was preferring not to use the
            > absolute path, "http://myserver...", in the link reference as the URL
            > is different for our development, test and production environments.
            > In the interest of just getting it to work, I coded in the absolute
            > path to my production server and made sure to put the .ico file in an
            > "images" directory so that it would work for dev, test and prod, only
            > pointing to the production file for each instance. i.e.
            > "http://ProductionServe r/MyApp/images/myIcon.ico"
            >
            > <I hope I haven't completely caused eyes to glaze over> ;-)
            >
            > Again, to my dismay... the icon was picked up when accessing the page
            > via HTTP and missing when accessing via HTTPS?[/color]

            On different browsers? It couldn't just be a case of browser
            configuration to ignore mixed content (secure/non-secure) on a page?

            Note that what you're doing is bad news, for that reason. It'll throw
            up security warnings at people.

            --
            My "from" address is totally fake. (Hint: If I wanted e-mails from
            complete strangers, I'd have put a real one, there.) Reply to usenet
            postings in the same place as you read the message you're replying to.

            Comment

            • Todd Peterson

              #7
              Re: &lt;link&gt; - &quot;rel='shor tcut icon'&quot; Not Working with HTTPS???

              Thanks again to all for the responses! I had a co-worker access the
              page from his browser and voila... Apparently, it is a browser
              security setting! Now... to find out which one... ;-)

              I sincerely appreciate everyone taking the time to respond, ultimately
              leading me to identification of the problem!!!

              Best Regards,
              Todd

              Tim <admin@sheerhel l.lan> wrote in message news:<62fsjv081 64svj1imtqiujrs aqd38gbv8f@4ax. com>...[color=blue]
              > On 15 Aug 2003 15:49:31 -0700,
              > todd_peterson@b illing.com (Todd Peterson) wrote:
              >[color=green]
              > > We are running IIS and as far as I know, there is only one document
              > > root "inetpub\wwwroo t\myapp". I was preferring not to use the
              > > absolute path, "http://myserver...", in the link reference as the URL
              > > is different for our development, test and production environments.
              > > In the interest of just getting it to work, I coded in the absolute
              > > path to my production server and made sure to put the .ico file in an
              > > "images" directory so that it would work for dev, test and prod, only
              > > pointing to the production file for each instance. i.e.
              > > "http://ProductionServe r/MyApp/images/myIcon.ico"
              > >
              > > <I hope I haven't completely caused eyes to glaze over> ;-)
              > >
              > > Again, to my dismay... the icon was picked up when accessing the page
              > > via HTTP and missing when accessing via HTTPS?[/color]
              >
              > On different browsers? It couldn't just be a case of browser
              > configuration to ignore mixed content (secure/non-secure) on a page?
              >
              > Note that what you're doing is bad news, for that reason. It'll throw
              > up security warnings at people.[/color]

              Comment

              Working...