From: bugzilla-daemon@libre-riscv.org
To: libre-riscv-dev@lists.libre-riscv.org
Subject: [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway
Date: Tue, 07 Apr 2020 14:58:41 +0000
Message-ID: <bug-185-13-krlOIfCmhf@http.bugs.libre-riscv.org/> (raw)
In-Reply-To: <bug-185-13@http.bugs.libre-riscv.org/>
http://bugs.libre-riscv.org/show_bug.cgi?id=185
--- Comment #16 from Alain D D Williams <addw@phcomp.co.uk> ---
All done - except a quick tidy up - removing old config commented out.
Done:
* all libre-riscv sites redirect to a corresponding libre-soc site
* all http:// sites redirect to a https:// site
This might mean that web browsers will not auto fill passwords, since they are
looking at different domains.
Also: what to do with uelves.com ? What is this ?
--
You are receiving this mail because:
You are on the CC list for the bug.
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-185-13@http.bugs.libre-riscv.org/>
2020-04-02 17:50 ` [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway when accessing bugzilla from archive.org bugzilla-daemon
2020-04-02 18:26 ` [libre-riscv-dev] [Bug 185] Getting 502 Bad Gateway bugzilla-daemon
2020-04-03 18:32 ` bugzilla-daemon
2020-04-03 18:50 ` bugzilla-daemon
2020-04-06 21:32 ` bugzilla-daemon
2020-04-06 21:55 ` bugzilla-daemon
2020-04-07 11:02 ` bugzilla-daemon
2020-04-07 11:21 ` bugzilla-daemon
2020-04-07 11:35 ` bugzilla-daemon
2020-04-07 11:37 ` bugzilla-daemon
2020-04-07 14:58 ` bugzilla-daemon [this message]
2020-04-07 15:01 ` bugzilla-daemon
2020-04-07 15:04 ` bugzilla-daemon
2020-04-07 15:31 ` bugzilla-daemon
[not found] <bug-185-13@https.bugs.libre-soc.org/>
2020-04-07 15:50 ` bugzilla-daemon
2020-04-07 16:29 ` bugzilla-daemon
2020-04-15 17:06 ` bugzilla-daemon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-185-13-krlOIfCmhf@http.bugs.libre-riscv.org/ \
--to=bugzilla-daemon@libre-riscv.org \
--cc=libre-riscv-dev@lists.libre-riscv.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git