[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-bugs-dist
Subject:    [Bug 101851] New: favicon not shown while properly defined in HTML
From:       Mathieu Roy <yeupou () coleumes ! org>
Date:       2005-03-18 22:38:01
Message-ID: 20050318233755.101851.yeupou () coleumes ! org
[Download RAW message or body]

------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
         
http://bugs.kde.org/show_bug.cgi?id=101851         
           Summary: favicon not shown while properly defined in HTML tag
                    link rel="icon" type="image/png": related to HTTPS /
                    HTTP?
           Product: konqueror
           Version: 3.3.2
          Platform: unspecified
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: normal
          Priority: NOR
         Component: general
        AssignedTo: konq-bugs kde org
        ReportedBy: yeupou coleumes org


Version:           3.3.2 (using KDE 3.3.2,  (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-6)
OS:                Linux (i686) release 2.6.8-2-686-smp

Hello,

At https://gna.org/index.php the favicon is not shown, at https://savannah.gnu.org/ and \
https://savannah.cern.ch/ it is.

These 3 sites use the same software, same version, the same icon and the same HTML to render icon:

  <link rel="icon" type="image/png" ref="/images/$theme.theme/icon.png" />

The icon is perfectly loaded by mozilla on the 3 sites.

The only sensible explanation I can come up with is that Konqueror disregard the ref= content and assume \
it can goes http, not https, to get the icon, even if the loaded page is https. This works on 2 sites \
that provides both http and https. This indeed does not work on the third website that provides only \
https.

I think that konqueror should not assume that http or anyelse protocol is available. If he got a relative \
path, with no protocol specified, he should stick to it. HTTPS it is? HTTPS is will be.

But maybe that's not the cause of the problem. Tell me if you need more details.

Thanks,
Regards,


[prev in list] [next in list] [prev in thread] [next in thread]