https

[rs]

The old web site used to support https access. The new web site redirects https to http. This is unfortunate, because for some reason (which is true in my case) a https connection is able to traverse certain kinds of firewall filters whereas a https cannot. Plus a https connection cannot be "easily" monitored.

I don't know why there was the change. Is there an extra cost with https?

 

[jordifs]

¿Can you clarify which site?

For me this works fine:
https://www.cassiopaea.org/

A warning is raised because some 'images' or 'resources' are linked on HTTP (not all are available HTTPS).

 

[Ellipse]

Work for me too.
I was not aware of this ! SOTT editors, why don't you promote it ?

 

[Skyalmian]

Using a Mozilla add-on such as NoScript @http://noscript.net/ , one can force HTTPS on specific sites such as this. :)

 

[rs]

Well, I don't always control which browser I can use, but *something* is redirecting https to http, and this started to happen exactly coincident with the new design.

Strange.

 

[Skyalmian]

Hardcoded links are the only think I can think of, where http:// and the domain name are explicitly made for the link instead of, for example, "/category/volumes/the-wave/".

 

[Sirius]

Wow, I didn't know that cassiopaea.org supports https. I think, I will use the secure connection. I have NoScript (the Firefox addon, not no script ;D), so I could use the option which Skyalmian suggested.