|
From: | Kai Torben Ohlhus |
Subject: | [Octave-bug-tracker] [bug #59035] [octave forge] (website) Viewing pushed patches using https now requires a username & password |
Date: | Tue, 1 Sep 2020 02:08:25 -0400 (EDT) |
User-agent: | Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/85.0.4183.83 Safari/537.36 |
Update of bug #59035 (project octave): Status: Confirmed => Wont Fix Open/Closed: Open => Closed _______________________________________________________ Follow-up Comment #6: @OP: Maybe HTTPS Everywhere did not replace the protocol previously. In general everything "works as expected". It is documented here: https://sourceforge.net/p/forge/documentation/Mercurial/#developer-access-readwrite If you mind this HTTP/HTTPS inconsistency, please file a bug report at SourceForge https://sourceforge.net/p/forge/feature-requests/ and sorry for the inconvenience. Using the SourceForge website and browsing the commits, the HTTPS URL to watch the patch inside their own web interface is https://sourceforge.net/p/octave/image/ci/a3540099c0adc51e1bcc18d1d95c8b7bcc157ef2/ Closing this item. There is nothing we can do. _______________________________________________________ Reply to this item at: <https://savannah.gnu.org/bugs/?59035> _______________________________________________ Message sent via Savannah https://savannah.gnu.org/
[Prev in Thread] | Current Thread | [Next in Thread] |