[bug #63166] HTTP client shouldn't silently use HTTP for TLS/SSL requests.

[Arthur A. Gleckler]

URL:
  <https://savannah.gnu.org/bugs/?63166>

                 Summary: HTTP client shouldn't silently use HTTP for TLS/SSL
requests.
                 Project: MIT/GNU Scheme
               Submitter: aag
               Submitted: Wed 05 Oct 2022 05:18:21 PM PDT
                Category: None
                Severity: 3 - Normal
                Priority: 5 - Normal
              Item Group: None
                  Status: None
                 Privacy: Public
             Assigned to: None
         Originator Name: 
        Originator Email: 
             Open/Closed: Open
         Discussion Lock: Any
                Keywords: 


    _______________________________________________________

Follow-up Comments:


-------------------------------------------------------
Date: Wed 05 Oct 2022 05:18:21 PM PDT By: Arthur A. Gleckler <aag>
When given an "https://"; URI, http-get and other procedures silently make HTTP
requests instead.  For example, here's a request for such a URI:


1 ]=> (http-get "https://speechcode.com/"; '())

;Value: #[http-response 380 301]


Note that the response is a 301, which on this web site is issued to redirect
HTTP URIs to equivalent TLS URIs.

Ideally, TLS would be supported, e.g. by linking GNUTLS.  But if it isn't
supported, an error should be signalled.







    _______________________________________________________

Reply to this item at:

  <https://savannah.gnu.org/bugs/?63166>

_______________________________________________
Message sent via Savannah
https://savannah.gnu.org/