[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

Wget downloaded and executed, and I'm receiving the following which looks to point to a possible problem with the recode of the uri to get to test SSL port 444:

wget -r http://choiceportal-d:8084
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = c:/progra~1/wget/etc/wgetrc
--2018-12-11 14:15:52--  http://choiceportal-d:8084/
Resolving choiceportal-d...,,, ...
Connecting to choiceportal-d||:8084... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://choiceportal-d:8084%:444{REQUEST_URI} [following]
https://choiceportal-d:8084%:444{REQUEST_URI}: Bad port number.

-----Original Message-----
From: Eric Covener <covener@xxxxxxxxx> 
Sent: Tuesday, December 11, 2018 11:31 AM
To: users@xxxxxxxxxxxxxxxx
Subject: Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

On Tue, Dec 11, 2018 at 11:28 AM Kathy S Durlacher <ksdurlacher@xxxxxxx> wrote:
> Yes, these non-standard ports are defined:
> Listen *:8084
> #Listen *:80
> Listen *:444
> #Listen *:443

I'd suggest debugging with a commnand-line client like wget or curl rather than a browser.  The former will give you more concrete error messages.

To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx