Opened 3 years ago

Last modified 2 years ago

#18160 new defect

Unable to access properly via HTTPS

Reported by: alive4ever@… Owned by:
Priority: highest Milestone:
Component: website Version: Trunk
Keywords: https tls wiki certificate-error mixed-contents Cc:


Since is the main information source for OpenWrt related stuff, it's required that is accessible via HTTPS. It's also better to enforce HTTPS by redirection and HSTS.

Why? Because the wiki needs to maintain the integrity of information it provides, either for users or wiki contributors.

It's good that other OpenWrt sites, such as forum, main site, and track, are available via HTTPS.

Currently, HTTPS is accessible on, but with certificate errors (Self-signed, domain mismatch) and mixed contents (static contents served from non HTTPS source, still using HTTP for POST), which greatly reduces the HTTPS usefulness for the site.

Some good wiki examples are and They implement HTTPS properly for the wiki site. They are under the same organization as OpenWrt (SPI, inc), so that I think there is no problem with the organization validity.

For your information, enabling HTTPS doesn't give any impact on server performance.

In case the webmaster doesn't know how to setup HTTPS properly, here is Google's presentation about "HTTPS everywhere"

This problem should be taken seriously and fixed as soon as possible.

Attachments (0)

Change History (3)

comment:1 Changed 2 years ago by…

While I see the benefits of https, there is also a notable drawback: cacheability.

comment:2 Changed 2 years ago by anonymous

May just be me, but it appears one can get at using HTTPS now.

comment:3 Changed 2 years ago by anonymous

I think this issue has been fixed for now.

Add Comment

Modify Ticket

as new .

E-mail address and user name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.