From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from hamza.pair.com (hamza.pair.com [209.68.5.143]) by sourceware.org (Postfix) with ESMTPS id 594573858D35 for ; Thu, 10 Nov 2022 10:03:16 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 594573858D35 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=pfeifer.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=pfeifer.com Received: from hamza.pair.com (localhost [127.0.0.1]) by hamza.pair.com (Postfix) with ESMTP id DDBFD33E6C; Thu, 10 Nov 2022 05:03:12 -0500 (EST) Received: from [10.30.2.25] (unknown [195.53.52.170]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by hamza.pair.com (Postfix) with ESMTPSA id 3E5A733E70; Thu, 10 Nov 2022 05:03:12 -0500 (EST) Date: Thu, 10 Nov 2022 11:03:10 +0100 (CET) From: Gerald Pfeifer To: =?ISO-8859-15?Q?Martin_Li=A8ka?= cc: gcc-patches@gcc.gnu.org Subject: Re: [DOCS] sphinx: use new Sphinx links In-Reply-To: Message-ID: <638cad2d-9463-ad35-4b67-d18b42027521@pfeifer.com> References: <482ae3dd-15f7-1e81-92e6-51a148e3bbc4@suse.cz> <2832f3b5-f815-3922-3681-edd55ca04dd5@suse.cz> <1656d2ca-f3b3-b46e-cf16-a6798e10deb1@suse.cz> <9c9b4969-dc72-a93b-335b-d72346bb437e@pfeifer.com> <8ae80e2a-9f49-4ebf-d7f0-815d32919573@suse.cz> <39fb5822-95aa-037a-5ac7-865e9096ff9f@pfeifer.com> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="8323328-1527026343-1668074592=:6261" X-Scanned-By: mailmunge 3.10 on 209.68.5.143 X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,KAM_DMARC_STATUS,KAM_SHORT,RCVD_IN_SBL_CSS,SPF_HELO_NONE,SPF_PASS,TXREP autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --8323328-1527026343-1668074592=:6261 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8BIT On Thu, 10 Nov 2022, Martin Liška wrote: >> https://gcc.gnu.org/install/ is back with a new face. > But it's not working properly due to some Content Security Policy: Hmm, it worked in my testing before and I just tried again: Firefox 106.0.1 (64-bit) and now also Chrome 106.0.5249.119 and w3m. Which browser are you using? Any particular add-ons or special security settings? > Refused to apply inline style because it violates the following Content > Security Policy directive: "default-src 'self' http: https:". Either the > 'unsafe-inline' keyword, a hash > ('sha256-wAI2VKPX8IUBbq55XacEljWEKQc4Xc1nmwVsAjAplNU='), or a nonce > ('nonce-...') is required to enable inline execution. Note also that > 'style-src' was not explicitly set, so 'default-src' is used as a fallback. That looks like it's related to some Javascript fun? Does sphinx pull in something? Ohhhh, it does. A lot. I'm not using any Javascript blocker, though, so not sure why I am not seeing any such warnings? Searching for "+sphinx" and this message did not result in anything. (It feels a bit curious how the position in the web server's file system or a symlink could trigger something like that?) Looking at the source code of index.html I am wondering about versus all the .js inclusions later on. And https://validator.w3.org/nu/?doc=https%3A%2F%2Fgcc.gnu.org%2Finstall%2F and https://validator.w3.org/nu/?doc=https%3A%2F%2Fgcc.gnu.org%2Fonlinedocs%2Finstall%2F appear equally (un)happy. Gerald --8323328-1527026343-1668074592=:6261--