× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.


  1.  Home
  2. MIDRANGE-L
  3. August 2023

Re: Help with HTTP server config

Hello Gio,

Am 14.08.2023 um 18:38 schrieb gio.cot via MIDRANGE-L <midrange-l@xxxxxxxxxxxxxxxxxx>:

I have a http Server that require ssl access; so, if in my browser i run
"https://mysite.com:443"; it works i expected . instead if i run
"http://mysite.com:443"; (http without "s") , i see the browser that run
to infinity without giving me any error.

That's quite normal. You're supposed to be consistent in your URL and ports.

Usually you don't need to append ports. http-URLs automatically assume port 80, and https-URLs assume port 443. Both by default.

You only need to supply port information in your URL if the ports on the server are non-standard. Otherwise let the browser sort out the port by URL type. Problem solved.

Instead i was waiting an error like "ERR_NAME_NOT_RESOLVED" or similar .


This is not possible, because you force a protocol mismatch (plain text vs. tls).

:wq! PoC




As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.