Caveat: what follows is my own understanding, but please be
aware that I'm not a member of the Betsie development team
and therefore cannot speak authoritatively.
Currently, Betsie doesn't support HTTPS (the TLS/SSL code is
not present to allow it to do so) and it would take a lot of
work to make it do so 'securely'. I'm sure Perl has
appropriate packages which could be used to implement it,
though.
Betsie is basically a non-caching proxy web server which
transforms pages before passing them on. This works fairly
well for HTTP, but there are some fundamental security
issues for HTTPS which would need to be addressed; in
particular, no 'betsiefied' https page can bear the originating
site's certificate unless the betsie server was co-located with
the original site (admittedly a common configuration).
Without that, betsified pages could only bear the certificate of
the Betsie server; whether that provides sufficient assurance
about the original site's content to the end user is doubtful in
general.
Your error page indicates a timeout occurred; this is almost
certainly because Betsie was trying to contact the server on
port 80 (http) rather than 443 (https), even though the url
scheme is https. Betsie just isn't that sophisticated.
/vis
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Betsie error for https.
Logged In: YES
user_id=744270
Caveat: what follows is my own understanding, but please be
aware that I'm not a member of the Betsie development team
and therefore cannot speak authoritatively.
Currently, Betsie doesn't support HTTPS (the TLS/SSL code is
not present to allow it to do so) and it would take a lot of
work to make it do so 'securely'. I'm sure Perl has
appropriate packages which could be used to implement it,
though.
Betsie is basically a non-caching proxy web server which
transforms pages before passing them on. This works fairly
well for HTTP, but there are some fundamental security
issues for HTTPS which would need to be addressed; in
particular, no 'betsiefied' https page can bear the originating
site's certificate unless the betsie server was co-located with
the original site (admittedly a common configuration).
Without that, betsified pages could only bear the certificate of
the Betsie server; whether that provides sufficient assurance
about the original site's content to the end user is doubtful in
general.
Your error page indicates a timeout occurred; this is almost
certainly because Betsie was trying to contact the server on
port 80 (http) rather than 443 (https), even though the url
scheme is https. Betsie just isn't that sophisticated.
/vis