W3C
We recently announced that we are planning to start redirecting all of www.w3.org to https, as is commonly done elsewhere. To get an understanding of whether this change is feasible for our site and what issues might arise, we conducted some limited tests of this configuration change, on August 1 and August 18-19. Here are […]
More…
W3C’s main web site www.w3.org has been available via https for over a decade, but until now we have not been redirecting all requests to https as is commonly done on most other sites. The primary reason for this is that we wanted to avoid causing issues for software requesting machine-readable resources from www.w3.org such […]
More…
W3C’s main web site www.w3.org is load-balanced over a number of servers using the excellent HAProxy load balancing software. Before we discovered HAProxy we used round-robin DNS for a number of years, with www.w3.org rotated among a number of servers with names like web1.w3.org, web2.w3.org, etc. One unfortunate side effect of this practice was that […]
More…
There are a number of email message headers that people may use to filter messages from W3C lists. The best header to use for this purpose is List-Id: (specified in RFC 2919), because this header is intended to remain constant throughout the lifetime of a list. Using other headers to filter mail from our lists […]
More…
Some of W3C’s most important system services are our mailing lists and corresponding online archives. Thousands of people participate in these lists, and the archives now contain millions of messages dating back to 1991. These archives are an essential resource for groups collaborating on standards work, to build shared context and record the history behind […]
More…
Copyright © 2023 World Wide Web Consortium. W3C® liability, trademark and permissive document license rules apply.