Opened 8 years ago

Closed 5 years ago

#40479 closed defect (fixed)

https://trac.macports.org loads MacPorts.png over http

Reported by: stevecheckoway (Stephen Checkoway) Owned by: admin@…
Priority: Normal Milestone:
Component: server/hosting Version:
Keywords: Cc:
Port:

Description

When trac.macports.org is loaded over https, it loads the MacPorts.png image at the top of the page over http:

<img alt="project logo" src="http://www.macosforge.org/files/logos/MacPorts.png">

This can be fixed by replacing the "http://" with "":

<img alt="project logo" src="//www.macosforge.org/files/logos/MacPorts.png">

or by using the same mechanism the MacOS forge logo uses.

Change History (7)

comment:1 Changed 8 years ago by stevecheckoway (Stephen Checkoway)

That should read, "This can be fixed by replacing the http:// with //"

comment:2 Changed 8 years ago by ryandesign (Ryan Schmidt)

Component: websiteserver/hosting
Owner: changed from jmpp@… to admin@…
Version: 2.2.0

comment:3 Changed 8 years ago by ryandesign (Ryan Schmidt)

That image also links to http://www.macports.org/ even if one is looking at Trac via https. Basically all complete URLs to other MacPorts or Mac OS Forge hostnames should begin with "//", not a protocol, assuming the hostnames in question are accessible via both http and https (and if they're not, we should probably make them work that way).

comment:4 Changed 8 years ago by wsiegrist@…

Owner: changed from admin@… to ryandesign@…

Should be fixed. Did I miss any?

comment:5 Changed 8 years ago by stevecheckoway (Stephen Checkoway)

The mixed content (loading images over HTTP) seems to be fixed. ryandesign's comment to change all absolute URLs to protocol-relative was not done. There are a bunch of links to MacPorts and Mac OS Forge hosts that are explicitly over http.

comment:6 Changed 5 years ago by ryandesign (Ryan Schmidt)

Owner: changed from ryandesign to admin@…
Status: newassigned

comment:7 Changed 5 years ago by ryandesign (Ryan Schmidt)

Resolution: fixed
Status: assignedclosed

I believe this has been fixed with our new Trac setup.

Note: See TracTickets for help on using tickets.