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

2018-12-11 Thread Kathy S Durlacher
Updated as suggested, and getting a different response -- "The requested URL / 
was not found on this server.  IBM_HTTP_Server Server at choiceportal-d Port 
8084"
Following is the wget response:

wget -r http://choiceportal-d:8084
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = c:/progra~1/wget/etc/wgetrc
--2018-12-11 15:46:43--  http://choiceportal-d:8084/
Resolving choiceportal-d... 10.90.231.36, 10.90.227.6, 10.90.231.6, ...
Connecting to choiceportal-d|10.90.231.36|:8084... connected.
HTTP request sent, awaiting response... 404 Not Found
2018-12-11 15:46:43 ERROR 404: Not Found.

I thought I would compare wget responses when issued against the V8.5 server 
running port 80/443:

wget -r http://choiceportal-d
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = c:/progra~1/wget/etc/wgetrc
--2018-12-11 15:44:01--  http://choiceportal-d/
Resolving choiceportal-d... 10.90.227.6, 10.90.231.6, 10.90.227.36, ...
Connecting to choiceportal-d|10.90.227.6|:80... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://choiceportal-d/ [following]
--2018-12-11 15:44:01--  https://choiceportal-d/
Connecting to choiceportal-d|10.90.227.6|:443... connected.
ERROR: cannot verify choiceportal-d's certificate, issued by 
`/C=US/ST=Ohio/L=Columbus/O=KSD Co/OU=Complex - Middleware/CN=KSD Root CA 
(2014)/emailAddress=middlew...@ksdco.com':
  Self-signed certificate encountered.
To connect to choiceportal-d insecurely, use `--no-check-certificate'.
Unable to establish SSL connection.



-Original Message-
From: Eric Covener  
Sent: Tuesday, December 11, 2018 2:57 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test 
HTTP Server with SSL

On Tue, Dec 11, 2018 at 2:55 PM Kathy S Durlacher  wrote:
>
> Hi Eric -- first let me thank you for your help - truly appreciated.
> Can you please respond placing a space following your https so what 
> you typed is not converted to https: //urldefense, etc

Here's the same reply in a pastebin: 
https://urldefense.proofpoint.com/v2/url?u=https-3A__hastebin.com_carinejiza.rb=DwIFaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=kL7VfANtCBW4zaxP9Qmei6Jjfa1PmkmMPCSV5Gtn7gk=3BAoctDUOBpMBekjUloivu2wkNFjXyXPAUuQcPmUjYI=


>
> -Original Message-
> From: Eric Covener 
> Sent: Tuesday, December 11, 2018 2:38 PM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help 
> Creating Test HTTP Server with SSL
>
> On Tue, Dec 11, 2018 at 2:28 PM Kathy S Durlacher  wrote:
> >
> > 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
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__choiceportal-2Dd
> > -3 
> > A8084=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxM
> > cp 
> > AKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=Hn2s
> > RZ fbdwSFMpwQbtwzVP6C13LRSlP1neHVTdxEk_w=
> > SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = 
> > c:/progra~1/wget/etc/wgetrc
> > --2018-12-11 14:15:52--
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__choiceportal-2Dd
> > -3 
> > A8084_=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sx
> > Mc
> > pAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=Z1K
> > u4 PNvTIRX8xS84CHU8OeLaiSyJ4TLEcKo-etjiOw=
> > Resolving choiceportal-d... 10.90.231.6, 10.90.227.36, 10.90.231.36, ...
> > Connecting to choiceportal-d|10.90.231.6|:8084... connected.
> > HTTP request sent, awaiting response... 302 Found
> > Location:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__choiceportal-2D
> > d- 
> > 3A8084-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKC
> > rS 
> > ug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6
> > RZ 
> > N86-K0yWidsrOWS4qo0a8tl0=81zStjCRKeLJ2lVhmd-A2QZeU5Pnb5FRs3nvWZNrN
> > HA
> > = [following]
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__choiceportal-2Dd-3A8084-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=81zStjCRKeLJ2lVhmd-A2QZeU5Pnb5FRs3nvWZNrNHA=:
> >  Bad port number.
>
> > RewriteRule (.*)
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__-25-257BHTTP-5F
> > HO 
> > ST-257D-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZK
> > Cr 
> > Sug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI
> > 6R 
> > ZN86-K0yWidsrOWS4qo0a8tl0=MZC41HKyztCxHZmWU7441g8Y5XAdfrvbGpORVfNR
> > MF
> > o=
>
> The % should be after 

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

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 2:55 PM Kathy S Durlacher  wrote:
>
> Hi Eric -- first let me thank you for your help - truly appreciated.
> Can you please respond placing a space following your https so what you typed 
> is not converted to https: //urldefense, etc

Here's the same reply in a pastebin: https://hastebin.com/carinejiza.rb


>
> -Original Message-
> From: Eric Covener 
> Sent: Tuesday, December 11, 2018 2:38 PM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating 
> Test HTTP Server with SSL
>
> On Tue, Dec 11, 2018 at 2:28 PM Kathy S Durlacher  wrote:
> >
> > 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
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__choiceportal-2Dd-3
> > A8084=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcp
> > AKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=Hn2sRZ
> > fbdwSFMpwQbtwzVP6C13LRSlP1neHVTdxEk_w=
> > SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc =
> > c:/progra~1/wget/etc/wgetrc
> > --2018-12-11 14:15:52--
> > https://urldefense.proofpoint.com/v2/url?u=http-3A__choiceportal-2Dd-3
> > A8084_=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMc
> > pAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=Z1Ku4
> > PNvTIRX8xS84CHU8OeLaiSyJ4TLEcKo-etjiOw=
> > Resolving choiceportal-d... 10.90.231.6, 10.90.227.36, 10.90.231.36, ...
> > Connecting to choiceportal-d|10.90.231.6|:8084... connected.
> > HTTP request sent, awaiting response... 302 Found
> > Location:
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__choiceportal-2Dd-
> > 3A8084-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCrS
> > ug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZ
> > N86-K0yWidsrOWS4qo0a8tl0=81zStjCRKeLJ2lVhmd-A2QZeU5Pnb5FRs3nvWZNrNHA
> > = [following]
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__choiceportal-2Dd-3A8084-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=81zStjCRKeLJ2lVhmd-A2QZeU5Pnb5FRs3nvWZNrNHA=:
> >  Bad port number.
>
> > RewriteRule (.*)
> > https://urldefense.proofpoint.com/v2/url?u=https-3A__-25-257BHTTP-5FHO
> > ST-257D-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCr
> > Sug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6R
> > ZN86-K0yWidsrOWS4qo0a8tl0=MZC41HKyztCxHZmWU7441g8Y5XAdfrvbGpORVfNRMF
> > o=
>
> The % should be after the :444.
>
> But more importantly, %{HTTP_HOST} will already contain the port if a 
> non-standard port was used for HTTP.  So tacking on :444 will not work.
> Here is one recipe to isolate the host and port and use the host in the 
> redirect:
>
> RewriteEngine On
> RewriteCond %{HTTP_HOST}  (.*?)(:\d+)?$
> RewriteRule ^/(.*) 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__-251-3A444_-241=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=ZAWVhJBD8g-6RVn5YlZIOKuNPRNxrmzGTxr9dFAcomg=
>
> %1 refers to the capture in the preceding condition.  The other change to the 
> RewriteRule is personal preference of having the / be outside the capture and 
> explicit in the substitution for readability.
>
>
> RewriteCond %{HTTP_HOST}  (.*):?\d*)
> RewriteRule (.*) 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__-251-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=JXRuQwB0SDLrOBiiAleYS5yJ5Lup65CGzBp3YJjug3c=
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>


-- 
Eric Covener
cove...@gmail.com

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2018-12-11 Thread Kathy S Durlacher
Hi Eric -- first let me thank you for your help - truly appreciated.  
Can you please respond placing a space following your https so what you typed 
is not converted to https: //urldefense, etc

-Original Message-
From: Eric Covener  
Sent: Tuesday, December 11, 2018 2:38 PM
To: users@httpd.apache.org
Subject: Re: [users@httpd] RE: [EXTERNAL] Re: [users@httpd] Help Creating Test 
HTTP Server with SSL

On Tue, Dec 11, 2018 at 2:28 PM Kathy S Durlacher  wrote:
>
> 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 
> https://urldefense.proofpoint.com/v2/url?u=http-3A__choiceportal-2Dd-3
> A8084=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcp
> AKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=Hn2sRZ
> fbdwSFMpwQbtwzVP6C13LRSlP1neHVTdxEk_w=
> SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc syswgetrc = 
> c:/progra~1/wget/etc/wgetrc
> --2018-12-11 14:15:52--  
> https://urldefense.proofpoint.com/v2/url?u=http-3A__choiceportal-2Dd-3
> A8084_=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMc
> pAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=Z1Ku4
> PNvTIRX8xS84CHU8OeLaiSyJ4TLEcKo-etjiOw=
> Resolving choiceportal-d... 10.90.231.6, 10.90.227.36, 10.90.231.36, ...
> Connecting to choiceportal-d|10.90.231.6|:8084... connected.
> HTTP request sent, awaiting response... 302 Found
> Location: 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__choiceportal-2Dd-
> 3A8084-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCrS
> ug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZ
> N86-K0yWidsrOWS4qo0a8tl0=81zStjCRKeLJ2lVhmd-A2QZeU5Pnb5FRs3nvWZNrNHA
> = [following]
> https://urldefense.proofpoint.com/v2/url?u=https-3A__choiceportal-2Dd-3A8084-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=81zStjCRKeLJ2lVhmd-A2QZeU5Pnb5FRs3nvWZNrNHA=:
>  Bad port number.

> RewriteRule (.*) 
> https://urldefense.proofpoint.com/v2/url?u=https-3A__-25-257BHTTP-5FHO
> ST-257D-25-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCr
> Sug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6R
> ZN86-K0yWidsrOWS4qo0a8tl0=MZC41HKyztCxHZmWU7441g8Y5XAdfrvbGpORVfNRMF
> o=

The % should be after the :444.

But more importantly, %{HTTP_HOST} will already contain the port if a 
non-standard port was used for HTTP.  So tacking on :444 will not work.
Here is one recipe to isolate the host and port and use the host in the 
redirect:

RewriteEngine On
RewriteCond %{HTTP_HOST}  (.*?)(:\d+)?$
RewriteRule ^/(.*) 
https://urldefense.proofpoint.com/v2/url?u=https-3A__-251-3A444_-241=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=ZAWVhJBD8g-6RVn5YlZIOKuNPRNxrmzGTxr9dFAcomg=

%1 refers to the capture in the preceding condition.  The other change to the 
RewriteRule is personal preference of having the / be outside the capture and 
explicit in the substitution for readability.


RewriteCond %{HTTP_HOST}  (.*):?\d*)
RewriteRule (.*) 
https://urldefense.proofpoint.com/v2/url?u=https-3A__-251-3A444-257BREQUEST-5FURI-257D=DwIBaQ=gMbiD-Q9WoaRgoXZKCrSug=S_61YgkDZJZT-cThGRSCt-9sxMcpAKVXN1DxEm4Z5Qk=gOJXDRuKVpX7vvZI6RZN86-K0yWidsrOWS4qo0a8tl0=JXRuQwB0SDLrOBiiAleYS5yJ5Lup65CGzBp3YJjug3c=

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 2:28 PM Kathy S Durlacher  wrote:
>
> 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... 10.90.231.6, 10.90.227.36, 10.90.231.36, ...
> Connecting to choiceportal-d|10.90.231.6|: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.

> RewriteRule (.*) https://%{HTTP_HOST}%:444{REQUEST_URI}

The % should be after the :444.

But more importantly, %{HTTP_HOST} will already contain the port if a
non-standard port was used for HTTP.  So tacking on :444 will not
work.
Here is one recipe to isolate the host and port and use the host in
the redirect:

RewriteEngine On
RewriteCond %{HTTP_HOST}  (.*?)(:\d+)?$
RewriteRule ^/(.*) https://%1:444/$1

%1 refers to the capture in the preceding condition.  The other change
to the RewriteRule is personal preference of having the / be outside
the capture and explicit in the substitution for readability.


RewriteCond %{HTTP_HOST}  (.*):?\d*)
RewriteRule (.*) https://%1:444{REQUEST_URI}

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2018-12-11 Thread Kathy S Durlacher
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... 10.90.231.6, 10.90.227.36, 10.90.231.36, ...
Connecting to choiceportal-d|10.90.231.6|: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  
Sent: Tuesday, December 11, 2018 11:31 AM
To: users@httpd.apache.org
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  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-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2018-12-11 Thread Eric Covener
On Tue, Dec 11, 2018 at 11:28 AM Kathy S Durlacher  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-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org



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

2018-12-11 Thread Kathy S Durlacher
Yes, these non-standard ports are defined:
Listen *:8084
#Listen *:80 
Listen *:444 
#Listen *:443

-Original Message-
From: Eric Covener  
Sent: Tuesday, December 11, 2018 11:12 AM
To: users@httpd.apache.org
Subject: [EXTERNAL] Re: [users@httpd] Help Creating Test HTTP Server with SSL

This is an EXTERNAL email. STOP. THINK before you CLICK links or OPEN 
attachments. If suspicious please click the 'Report to Incidents' button in 
Outlook or forward to incide...@aep.com from a mobile device.

**
> How defined in test version 9 using 8084 & SSL 444
>
> 


Did you add `Listen` directives for these non-standard ports?

-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org


-
To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
For additional commands, e-mail: users-h...@httpd.apache.org