On 04-11-2014 15:34, Bruce Dubbs wrote: > Fernando de Oliveira wrote: > >> http://archive.apache.org/dist/xmlgraphics/fop/source/ >> >> works fine (https also works with this URL). > > Not for me: > > The requested URL /dist/xmlgraphics/fop/source/ was not found on this > server. > > Perhaps a specific server issue: > > ;; ANSWER SECTION: > archive.apache.org. 1229 IN A 54.172.167.43 > archive.apache.org. 1229 IN A 192.87.106.229 > > 192.87.106.229 works. 54.172.167.43 gives weird results. > > https://archive.apache.org/dist/xmlgraphics/fop/source/ works though. > > There are a lot of sites disabling sslv3 due to a security issue. They > also really want to use https. We'll just need to keep on top of this. > Please change to https for any sites that you know use it.
Will do, thanks. In case you have interest, the add-on is at: https://www.eff.org/https-everywhere FF version works in seamonkey (it is a .xpi) I wrote something wrong in a previous post: it essentially has a white list of sites with https which is periodically updated (see in the following). https://www.eff.org/https-everywhere/faq/ {{{ Q. Why use a whitelist of sites that support HTTPS? Why can't you try to use HTTPS for every last site, and only fall back to HTTP if it isn't available? A. There are several problems with the idea of trying to automatically detect HTTPS on every site. Firstly, there is no guarantee that sites are going to give the same response via HTTPS that they give via HTTP. As of 2010, LiveJournal is a good example of this problem: compare these HTTP and HTTPS responses. Secondly, we don't think it's possible to test for HTTPS in real time without introducing security vulnerabilities (What should the extension do if the HTTPS connection attempt fails? Falling back to insecure HTTP isn't safe). Lastly, in some cases, HTTPS Everywhere has to perform quite complicated transformations on URIs — for example until recently the Wikipedia rule had to turn an address like http://en.wikipedia.org/wiki/World_Wide_Web into one like https://secure.wikimedia.org/wikipedia/en/wiki/World_Wide_Web because HTTPS was not available on Wikipedia's usual domains. }}} There is often the question (also in the faq page): {{{ Q. Why isn't HTTPS Everywhere available for download from addons.mozilla.org like most other Firefox add-ons? https://lists.eff.org/pipermail/https-everywhere/2014-April/002050.html }}} -- []s, Fernando -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
