[users@httpd] apache sending mail with subject “2.2.2.2 not in hosts list”

[aye coder]

I recently updated my server's IP address.  After restarting services,
apache began sending mail (from the apa...@box.example.com) with the
subject "2.2.2.2 not in hosts list". There is no body to the email -
just that subject.

This message is sent once every minute from UID 48 (apache).

System Information:
-
[acoder@box ~]# httpd -v
Server version: Apache/2.2.15 (Unix)
Server built:   May 11 2016 19:28:33

[acoder@box ~]# cat /etc/redhat-release
CentOS release 6.8 (Final)

[acoder@box ~]# hostname
box.example.com

[acoder@box ~]# ifconfig
inet addr:2.2.2.2



Example from /var/log/maillog
-
Jun 26 08:25:02 box postfix/pickup[13188]: 165881C0232: uid=48 from=
Jun 26 08:25:02 box postfix/cleanup[18593]: 165881C0232:
message-id=<20160626122502.165881c0...@box.example.com>
Jun 26 08:25:02 box postfix/qmgr[9276]: 165881C0232:
from=, size=1404, nrcpt=1 (queue active)
Jun 26 08:25:02 box postfix/smtp[18777]: 165881C0232:
to=, relay=smtp.example.com[2.2.8.8]:25,
delay=0.25, delays=0.11/0.04/0.02/0.07, dsn=2.0.0, status=sent (250
2.0.0 u5QCP2qp020979 Message accepted for delivery)
Jun 26 08:25:02 box postfix/qmgr[9276]: 165881C0232: removed


from /var/log/httpd/access_log
-
2.2.2.2 - - [29/Jun/2016:20:11:01 -0400] "\x16\x03\x01\x01\x11\x01"
501 208 "-" "httpd/unix-directory" "-"
2.2.2.2 - - [29/Jun/2016:20:11:01 -0400] "\x16\x03\x01\x01\x11\x01"
501 208 "-" "httpd/unix-directory" "-"
2.2.2.2 - - [29/Jun/2016:20:12:01 -0400] "\x16\x03\x01\x01\x11\x01"
501 208 "-" "httpd/unix-directory" "-"
2.2.2.2 - - [29/Jun/2016:20:12:01 -0400] "\x16\x03\x01\x01\x11\x01"
501 208 "-" "httpd/unix-directory" "-"
2.2.2.2 - - [29/Jun/2016:20:12:01 -0400] "\x16\x03\x01\x01\x11\x01"
501 208 "-" "httpd/unix-directory" "-"


This server only handles requests over 443. There are no virtualhost
configurations for port 80.


Here's a trimmed down version of my /etc/httpd/conf.d/ssl.conf
-

LoadModule ssl_module modules/mod_ssl.so
Listen 443
ServerSignature Off
ServerTokens Prod

# clipped SSL config



ServerName box.example.com
ServerAdmin aco...@box.example.com
DocumentRoot /var/www/html/

TraceEnable off

Header always append X-Frame-Options DENY
Header set X-XSS-Protection: "1; mode=block"
Header set X-Content-Type-Options: nosniff
Header set X-WebKit-CSP: "default-src 'self'"
Header set X-Permitted-Cross-Domain-Policies: "master-only"
Header set Cache-Control "no-cache, no-store, must-revalidate"

Header set Pragma "no-cache"
Header set Expires 0

# clipped SSL config




On a whim I added the machine's IP to /etc/hosts:
--
[acoder@box ~]# vi /etc/hosts
# i
2.2.2.2 box.example.com
# :wq


Restarted the server and ran configtest to make sure:
--
[acoder@box ~]# service httpd restart
Stopping httpd:[  OK  ]
Starting httpd:[  OK  ]
[acoder@box ~]# apachectl configtest
Syntax OK


Apache httpd is serving pages as usual.


However, I continue to receive these unusual email notifications every
minute. As above, it is coming from the apache@ account.  If I change
my system's IP back to what it was before, the oddball emails stop.

I've tried rebooting the system to no avail.

I've also tried looking for the subject string on the local filesystem:
-
grep -r "not in hosts list" /etc/
grep -r "not in hosts list" /usr/
grep -r "not in hosts list" /var/


Nothing found.


The only instance of IP 2.2.2.2 is found in
---
/etc/sysconfig/network-scripts/em1-cfg
/etc/httpd/conf.d/ssl.conf (copied above)
/etc/httpd/conf.d/vhosts.conf
/etc/hosts



Googling is coming up empty. What would cause the apache account to
send out these vague messages?


Thanks,
JA

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

Re: [users@httpd] Date Format of Shell Program Changes in Apache

[Yehuda Katz]

This isn't a perl list, but I was playing around and found you can do this
in perl:

#!/usr/bin/perl
> use strict;
> BEGIN
> {
> $ENV{LC_TIME}= 'en_US.UTF-8';
> }
> print "content-type: text/plain\n\n";
> print `who`;
> print `locale`;



Hopefully that helps,

- Y

On Fri, Jul 1, 2016 at 5:50 PM, Yehuda Katz  wrote:

> This is because of the locale settings. I changed the script to show the
> locale (and to be plain text so the spaces are visible).
>
> #!/usr/bin/perl
>> use strict;
>> print "content-type: text/plain\n\n";
>> print `who`;
>> print `locale`;
>
>
> Apache shows this:
>
> yehuda   pts/2Jul  1 17:37 (pool-xx.washdc.fios.verizon.net)
>> LANG=
>> LANGUAGE=
>> LC_CTYPE="POSIX"
>> LC_NUMERIC="POSIX"
>> LC_TIME="POSIX"
>> LC_COLLATE="POSIX"
>> LC_MONETARY="POSIX"
>> LC_MESSAGES="POSIX"
>> LC_PAPER="POSIX"
>> LC_NAME="POSIX"
>> LC_ADDRESS="POSIX"
>> LC_TELEPHONE="POSIX"
>> LC_MEASUREMENT="POSIX"
>> LC_IDENTIFICATION="POSIX"
>> LC_ALL=
>
>
> And the command line shows this:
>
> content-type: text/plain
>>
>
>
> yehuda   pts/22016-07-01 17:37 (
>> pool-xx.washdc.fios.verizon.net)
>> LANG=en_US.UTF-8
>> LANGUAGE=
>> LC_CTYPE="en_US.UTF-8"
>> LC_NUMERIC="en_US.UTF-8"
>> LC_TIME="en_US.UTF-8"
>> LC_COLLATE="en_US.UTF-8"
>> LC_MONETARY="en_US.UTF-8"
>> LC_MESSAGES="en_US.UTF-8"
>> LC_PAPER="en_US.UTF-8"
>> LC_NAME="en_US.UTF-8"
>> LC_ADDRESS="en_US.UTF-8"
>> LC_TELEPHONE="en_US.UTF-8"
>> LC_MEASUREMENT="en_US.UTF-8"
>> LC_IDENTIFICATION="en_US.UTF-8"
>> LC_ALL=
>
>
>
> The environment variable that sets how the time is shown is LC_TIME.
> You can probably change this in your script (for example, php provides a
> way , perl likely has
> one too) and there is a third-party module that claims to set the locale
> for the whole server.
> Your OS might also give you a way to set it for the whole server.
>
> - Y
>
>
> On Fri, Jul 1, 2016 at 4:34 PM, Rob McAninch 
> wrote:
>
>> Server version: Apache/2.4.10 (Debian)
>>
>> This seems like it should be simple but manual pages and searching have
>> not shown me an answer yet. Reduced it to as simple as I can, I don't
>> understand why the date format is different in each.
>>
>> #!/usr/bin/perl
>> use strict;
>> print "content-type: text/html\n\n";
>> print `who`;
>>
>>
>> When I call it up in a web browser I get
>>
>> rob pts/1 Jul 1 12:28 (192.x.x.x)
>>
>> The same script on a command line via ssh I get:
>>
>> prompt$ perl tryme.cgi
>> content-type: text/html
>>
>> rob  pts/12016-07-01 12:28 (192.x.x.x)
>>
>>
>>
>> --
>> Rob
>>
>
>

Re: [users@httpd] Date Format of Shell Program Changes in Apache

[Yehuda Katz]

This is because of the locale settings. I changed the script to show the
locale (and to be plain text so the spaces are visible).

#!/usr/bin/perl
> use strict;
> print "content-type: text/plain\n\n";
> print `who`;
> print `locale`;


Apache shows this:

yehuda   pts/2Jul  1 17:37 (pool-xx.washdc.fios.verizon.net)
> LANG=
> LANGUAGE=
> LC_CTYPE="POSIX"
> LC_NUMERIC="POSIX"
> LC_TIME="POSIX"
> LC_COLLATE="POSIX"
> LC_MONETARY="POSIX"
> LC_MESSAGES="POSIX"
> LC_PAPER="POSIX"
> LC_NAME="POSIX"
> LC_ADDRESS="POSIX"
> LC_TELEPHONE="POSIX"
> LC_MEASUREMENT="POSIX"
> LC_IDENTIFICATION="POSIX"
> LC_ALL=


And the command line shows this:

content-type: text/plain
>


yehuda   pts/22016-07-01 17:37 (pool-xx.washdc.fios.verizon.net)
> LANG=en_US.UTF-8
> LANGUAGE=
> LC_CTYPE="en_US.UTF-8"
> LC_NUMERIC="en_US.UTF-8"
> LC_TIME="en_US.UTF-8"
> LC_COLLATE="en_US.UTF-8"
> LC_MONETARY="en_US.UTF-8"
> LC_MESSAGES="en_US.UTF-8"
> LC_PAPER="en_US.UTF-8"
> LC_NAME="en_US.UTF-8"
> LC_ADDRESS="en_US.UTF-8"
> LC_TELEPHONE="en_US.UTF-8"
> LC_MEASUREMENT="en_US.UTF-8"
> LC_IDENTIFICATION="en_US.UTF-8"
> LC_ALL=



The environment variable that sets how the time is shown is LC_TIME.
You can probably change this in your script (for example, php provides a way
, perl likely has one too)
and there is a third-party module that claims to set the locale for the
whole server.
Your OS might also give you a way to set it for the whole server.

- Y


On Fri, Jul 1, 2016 at 4:34 PM, Rob McAninch  wrote:

> Server version: Apache/2.4.10 (Debian)
>
> This seems like it should be simple but manual pages and searching have
> not shown me an answer yet. Reduced it to as simple as I can, I don't
> understand why the date format is different in each.
>
> #!/usr/bin/perl
> use strict;
> print "content-type: text/html\n\n";
> print `who`;
>
>
> When I call it up in a web browser I get
>
> rob pts/1 Jul 1 12:28 (192.x.x.x)
>
> The same script on a command line via ssh I get:
>
> prompt$ perl tryme.cgi
> content-type: text/html
>
> rob  pts/12016-07-01 12:28 (192.x.x.x)
>
>
>
> --
> Rob
>

[users@httpd] Date Format of Shell Program Changes in Apache

[Rob McAninch]

Server version: Apache/2.4.10 (Debian)

This seems like it should be simple but manual pages and searching have not
shown me an answer yet. Reduced it to as simple as I can, I don't
understand why the date format is different in each.

#!/usr/bin/perl
use strict;
print "content-type: text/html\n\n";
print `who`;


When I call it up in a web browser I get

rob pts/1 Jul 1 12:28 (192.x.x.x)

The same script on a command line via ssh I get:

prompt$ perl tryme.cgi
content-type: text/html

rob  pts/12016-07-01 12:28 (192.x.x.x)



-- 
Rob

Re: [users@httpd] ProxyPreserveHost doesn't work with SSL

[Yann Ylavic]

On Fri, Jul 1, 2016 at 6:26 PM, Marat Khalili  wrote:
>
> Because of SSL the problem is somewhat hard to debug, can't just packet
> trace. I tried to replace IIS application with CGI script on different
> Apache, without SSL, and found that ProxyPreserveHost is not ignored
> (environment variable SERVER_NAME set correctly to myapp.com). I guess for
> SSL the ProxyPreserveHost is implemented partially, i.e. for Host header but
> not for SNI. Any ideas on how to investigate?

Is the header Host sent by the proxy different from the one sent by
the client (with and without using SSL) or are you talking about the
SNI (in the SSL handshake) which is not set when using SSL?

In the latter case, you may need this fix released in from 2.4.20
(http://svn.apache.org/r1733474).

Regards,
Yann.

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

[users@httpd] ProxyPreserveHost doesn't work with SSL

[Marat Khalili]

Dear all,

I'm reverse proxying requests on Apache/2.4.18 (stock version on Ubuntu 
16.04) via SSL to an application running on IIS 7.0. Somehow, despite 
ProxyPreserveHost, IIS app manages to sniff IP-address 10.1.2.3 
specified in ProxyPass (see below) and breaks. If I replace 10.1.2.3 
with myapp.com and put "10.1.2.3 myapp.com" in /etc/hosts everything 
works (but I don't like the solution).


Because of SSL the problem is somewhat hard to debug, can't just packet 
trace. I tried to replace IIS application with CGI script on different 
Apache, without SSL, and found that ProxyPreserveHost is not ignored 
(environment variable SERVER_NAME set correctly to myapp.com). I guess 
for SSL the ProxyPreserveHost is implemented partially, i.e. for Host 
header but not for SNI. Any ideas on how to investigate?


Here's the complete virtualhost configuration:
---

ServerName myapp.com

SSLEngine on
SSLCertificateFile  /etc/ssl/certs/myapp.pem
SSLCertificateKeyFile /etc/ssl/private/myapp.key

SSLProxyEngine on
SSLProxyProtocol all
SSLProxyCipherSuite ALL
SSLProxyVerify none
SSLProxyCheckPeerCN off
SSLProxyCheckPeerName off
SSLProxyCheckPeerExpire off


ProxyPreserveHost on
ProxyPass https://10.1.2.3/ connectiontimeout=300 timeout=300
ProxyPassReverse /
ProxyPassReverseCookieDomain myapp.com 10.1.2.3


---

--

With Best Regards,
Marat Khalili

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

Re: [users@httpd] Last-Modified header overridden

[Luca Toscano]

2016-07-01 16:53 GMT+02:00 Vacelet, Manuel :

>
>
> On Fri, Jul 1, 2016 at 4:14 PM, Luca Toscano 
> wrote:
>
>>
>>
>> 2016-06-29 9:38 GMT+02:00 Luca Toscano :
>>
>>>
>>>
>>> 2016-06-28 18:32 GMT+02:00 Luca Toscano :
>>>


 2016-06-27 14:52 GMT+02:00 Vacelet, Manuel 
 :

>
>
> On Mon, Jun 27, 2016 at 2:17 PM, Luca Toscano 
> wrote:
>
>>
>>
>> 2016-06-27 13:17 GMT+02:00 Vacelet, Manuel <
>> manuel.vace...@enalean.com>:
>>
>>>
>>>
>>> On Sat, Jun 25, 2016 at 11:00 AM, Luca Toscano <
>>> toscano.l...@gmail.com> wrote:
>>>


 2016-06-24 17:26 GMT+02:00 Vacelet, Manuel <
 manuel.vace...@enalean.com>:

>
>
> On Sun, Jun 19, 2016 at 3:17 PM, Luca Toscano <
> toscano.l...@gmail.com> wrote:
>
>>
>>
>> 2016-06-08 16:14 GMT+02:00 Vacelet, Manuel <
>> manuel.vace...@enalean.com>:
>>
>>> On Tue, Jun 7, 2016 at 11:02 PM, Luca Toscano <
>>> toscano.l...@gmail.com> wrote:
>>>


 2016-06-07 10:55 GMT+02:00 Vacelet, Manuel <
 manuel.vace...@enalean.com>:

>
>
> On Mon, Jun 6, 2016 at 5:32 PM, Vacelet, Manuel <
> manuel.vace...@enalean.com> wrote:
>
>> dOn Mon, Jun 6, 2016 at 5:00 PM, Vacelet, Manuel <
>> manuel.vace...@enalean.com> wrote:
>>
>>> On Mon, Jun 6, 2016 at 4:09 PM, Luca Toscano <
>>> toscano.l...@gmail.com> wrote:
>>>

 I was able to repro building httpd from 2.4.x branch and
 following your configuration files on github. I am almost sure 
 that
 somewhere httpd sets the Last-Modified header translating 
 "foo" to the
 first Jan 1970 date. I realized though that I didn't recall 
 the real issue,
 since passing value not following the RFC can lead to 
 inconsistencies, so I
 went back and checked the correspondence. Quoting:

 "Actually I wrote this snippet to highlight the behaviour
 (the original code sent the date in iso8601 instead of 
 rfc1123) because it
 was more obvious.
 During my tests (this is extracted from an automated test
 suite), even after having converted dates to rfc1123, I 
 continued to get
 some sparse errors. What I got is that the value I sent was 
 sometimes
 slightly modified (a second or 2) depending on the machine 
 load."

 So my understanding is that you would like to know why a
 Last-Modified header with a legitimate date/time set by a PHP 
 app gets
 "delayed" by a couple of seconds from httpd, right?

>>>
>>> Yes for sure, this is the primary issue.
>>> However, the (undocumented) difference of behavior from one
>>> version to another (2.2 -> 2.4 and more surprisingly from 
>>> between two 2.4
>>> versions) is also in question here.
>>> Even more strange, 2.4 built for other distrib doesn't
>>> highlight the behaviour !
>>>
>>>
>>
>> I made another series of test and it seems to be linked to
>> fastcgi.
>>
>> I took the stock apache (2.4.6 plus tons of patches)  &
>> php-fpm (5.4.16 + tons of patches) from RHEL7 and I get the 
>> exact same
>> behaviour (headers rewritten to EPOCH)
>> However, if I server the very same php script from mod_php
>> (instead of fcgi) it "works" (the headers are not modified).
>>
>>
> For the record, I also have the same behaviour (headers
> rewritten when using php-fpm + fastcgi) on alpine linux 3.4 that
> ships apache2-2.4.20.
> So AFAICT, it doesn't seem distro specific.
>
> On the root of the problem, from my point of view:
> - the difference between mod_php vs. php-fpm + fcgi is
> understandable (even if not desired and not documented).
> - the fact that fcgi handler parse & rewrite headers seems to
> lead to inconsistencies (I'll try to build a test case for that).
> - however, even if the headers are wrong, I think apache
> default 

Re: [users@httpd] Last-Modified header overridden

[Vacelet, Manuel]

On Fri, Jul 1, 2016 at 4:14 PM, Luca Toscano  wrote:

>
>
> 2016-06-29 9:38 GMT+02:00 Luca Toscano :
>
>>
>>
>> 2016-06-28 18:32 GMT+02:00 Luca Toscano :
>>
>>>
>>>
>>> 2016-06-27 14:52 GMT+02:00 Vacelet, Manuel :
>>>


 On Mon, Jun 27, 2016 at 2:17 PM, Luca Toscano 
 wrote:

>
>
> 2016-06-27 13:17 GMT+02:00 Vacelet, Manuel  >:
>
>>
>>
>> On Sat, Jun 25, 2016 at 11:00 AM, Luca Toscano <
>> toscano.l...@gmail.com> wrote:
>>
>>>
>>>
>>> 2016-06-24 17:26 GMT+02:00 Vacelet, Manuel <
>>> manuel.vace...@enalean.com>:
>>>


 On Sun, Jun 19, 2016 at 3:17 PM, Luca Toscano <
 toscano.l...@gmail.com> wrote:

>
>
> 2016-06-08 16:14 GMT+02:00 Vacelet, Manuel <
> manuel.vace...@enalean.com>:
>
>> On Tue, Jun 7, 2016 at 11:02 PM, Luca Toscano <
>> toscano.l...@gmail.com> wrote:
>>
>>>
>>>
>>> 2016-06-07 10:55 GMT+02:00 Vacelet, Manuel <
>>> manuel.vace...@enalean.com>:
>>>


 On Mon, Jun 6, 2016 at 5:32 PM, Vacelet, Manuel <
 manuel.vace...@enalean.com> wrote:

> dOn Mon, Jun 6, 2016 at 5:00 PM, Vacelet, Manuel <
> manuel.vace...@enalean.com> wrote:
>
>> On Mon, Jun 6, 2016 at 4:09 PM, Luca Toscano <
>> toscano.l...@gmail.com> wrote:
>>
>>>
>>> I was able to repro building httpd from 2.4.x branch and
>>> following your configuration files on github. I am almost sure 
>>> that
>>> somewhere httpd sets the Last-Modified header translating "foo" 
>>> to the
>>> first Jan 1970 date. I realized though that I didn't recall the 
>>> real issue,
>>> since passing value not following the RFC can lead to 
>>> inconsistencies, so I
>>> went back and checked the correspondence. Quoting:
>>>
>>> "Actually I wrote this snippet to highlight the behaviour
>>> (the original code sent the date in iso8601 instead of rfc1123) 
>>> because it
>>> was more obvious.
>>> During my tests (this is extracted from an automated test
>>> suite), even after having converted dates to rfc1123, I 
>>> continued to get
>>> some sparse errors. What I got is that the value I sent was 
>>> sometimes
>>> slightly modified (a second or 2) depending on the machine 
>>> load."
>>>
>>> So my understanding is that you would like to know why a
>>> Last-Modified header with a legitimate date/time set by a PHP 
>>> app gets
>>> "delayed" by a couple of seconds from httpd, right?
>>>
>>
>> Yes for sure, this is the primary issue.
>> However, the (undocumented) difference of behavior from one
>> version to another (2.2 -> 2.4 and more surprisingly from 
>> between two 2.4
>> versions) is also in question here.
>> Even more strange, 2.4 built for other distrib doesn't
>> highlight the behaviour !
>>
>>
>
> I made another series of test and it seems to be linked to
> fastcgi.
>
> I took the stock apache (2.4.6 plus tons of patches)  &
> php-fpm (5.4.16 + tons of patches) from RHEL7 and I get the exact 
> same
> behaviour (headers rewritten to EPOCH)
> However, if I server the very same php script from mod_php
> (instead of fcgi) it "works" (the headers are not modified).
>
>
 For the record, I also have the same behaviour (headers
 rewritten when using php-fpm + fastcgi) on alpine linux 3.4 that
 ships apache2-2.4.20.
 So AFAICT, it doesn't seem distro specific.

 On the root of the problem, from my point of view:
 - the difference between mod_php vs. php-fpm + fcgi is
 understandable (even if not desired and not documented).
 - the fact that fcgi handler parse & rewrite headers seems to
 lead to inconsistencies (I'll try to build a test case for that).
 - however, even if the headers are wrong, I think apache
 default (use EPOCH) is wrong as it leads to very inconsistent 
 behaviour
 (the resource will never expire). I would prefer either:
 -- do not touch the header
 -- raise a 

RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4

[Joe Muller]

 I have not yet tried disabling KeepAlive.  For our IPlanet servers we have 
always had KeepAlive turned ON.   Also support recommended I make sure it is 
ON.  I guess I can try turning it off just to see what happens, but I imagine 
there is a performance hit leaving it like that.   I have tried increasing the 
KeepAlive timeout, and increasing the WLSocketTimeoutSecs and WLIOTimeoutSecs, 
but that did not help.

I also have not fiddled with ConnectRetrySecs or ConnectTimeoutsecs yet.  I 
didn't think would those were applicable here, since I increasing the sleep 
timeout would not be applicable.  Also our application has not been returning 
any 503 Service Unavailable responses.

-Joe




-Original Message-
From: Mike Rumph [mailto:mike.ru...@oracle.com] 
Sent: Friday, July 01, 2016 10:03 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 
to Apache 2.4

Hello Joe,

You can see the parameters that are available from the WLS plug-ins here:
-
https://docs.oracle.com/middleware/1213/webtier/PLGWL/plugin_params.htm#PLGWL475

The equivalent to what Yann was referring could be KeepAliveEnabled and 
KeepAliveSecs.
But ConnectTimeoutSecs, ConnectRetrySecs, WLSocketTimeoutSecs and 
WLIOTimeoutSecs might also be useful.

Thanks,

Mike

On 7/1/2016 3:06 AM, Joe Muller wrote:
> As far as we can see from fiddler and the Apache logs the request is fully 
> sent.   I assume those parameters you mentioned are for mod_proxy ?  We are 
> not using mod_proxy for this, we are using the Weblogic plug-in for Apache 
> 2.4.
>
> -Original Message-
> From: Yann Ylavic [mailto:ylavic@gmail.com]
> Sent: Friday, July 01, 2016 3:42 AM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun 
> One 6.1 to Apache 2.4
>
> On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller  wrote:
>>One interesting thing we did find on a packet capture on the back end 
>> between the proxy server and the application server is that 3 seconds after 
>> the proxy server apparently closed the port, the Weblogic application server 
>> tried to send data.  It almost like Weblogic did not realize the port was 
>> closed.  Very odd.
> Is the HTTP request fully sent (proxy) and responded (backend) when this 
> happens? (I try to understand why a backend/application would send data on 
> its own).
>
> Otherwise, on a general rule, did you take care that the TTL of proxy 
> connection (to the backend) is lower than the KeepAliveTimeout configured on 
> the backend?
> This can be done by using the ProxyPass/BalancerMember parameter ttl=...
> But before that, does disabling keepalive on the proxy help already?
> (ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive)
>
> Regards,
> Yann.
>
> -
> 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


-
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

Re: [users@httpd] Last-Modified header overridden

[Luca Toscano]

2016-06-29 9:38 GMT+02:00 Luca Toscano :

>
>
> 2016-06-28 18:32 GMT+02:00 Luca Toscano :
>
>>
>>
>> 2016-06-27 14:52 GMT+02:00 Vacelet, Manuel :
>>
>>>
>>>
>>> On Mon, Jun 27, 2016 at 2:17 PM, Luca Toscano 
>>> wrote:
>>>


 2016-06-27 13:17 GMT+02:00 Vacelet, Manuel 
 :

>
>
> On Sat, Jun 25, 2016 at 11:00 AM, Luca Toscano  > wrote:
>
>>
>>
>> 2016-06-24 17:26 GMT+02:00 Vacelet, Manuel <
>> manuel.vace...@enalean.com>:
>>
>>>
>>>
>>> On Sun, Jun 19, 2016 at 3:17 PM, Luca Toscano <
>>> toscano.l...@gmail.com> wrote:
>>>


 2016-06-08 16:14 GMT+02:00 Vacelet, Manuel <
 manuel.vace...@enalean.com>:

> On Tue, Jun 7, 2016 at 11:02 PM, Luca Toscano <
> toscano.l...@gmail.com> wrote:
>
>>
>>
>> 2016-06-07 10:55 GMT+02:00 Vacelet, Manuel <
>> manuel.vace...@enalean.com>:
>>
>>>
>>>
>>> On Mon, Jun 6, 2016 at 5:32 PM, Vacelet, Manuel <
>>> manuel.vace...@enalean.com> wrote:
>>>
 dOn Mon, Jun 6, 2016 at 5:00 PM, Vacelet, Manuel <
 manuel.vace...@enalean.com> wrote:

> On Mon, Jun 6, 2016 at 4:09 PM, Luca Toscano <
> toscano.l...@gmail.com> wrote:
>
>>
>> I was able to repro building httpd from 2.4.x branch and
>> following your configuration files on github. I am almost sure 
>> that
>> somewhere httpd sets the Last-Modified header translating "foo" 
>> to the
>> first Jan 1970 date. I realized though that I didn't recall the 
>> real issue,
>> since passing value not following the RFC can lead to 
>> inconsistencies, so I
>> went back and checked the correspondence. Quoting:
>>
>> "Actually I wrote this snippet to highlight the behaviour
>> (the original code sent the date in iso8601 instead of rfc1123) 
>> because it
>> was more obvious.
>> During my tests (this is extracted from an automated test
>> suite), even after having converted dates to rfc1123, I 
>> continued to get
>> some sparse errors. What I got is that the value I sent was 
>> sometimes
>> slightly modified (a second or 2) depending on the machine load."
>>
>> So my understanding is that you would like to know why a
>> Last-Modified header with a legitimate date/time set by a PHP 
>> app gets
>> "delayed" by a couple of seconds from httpd, right?
>>
>
> Yes for sure, this is the primary issue.
> However, the (undocumented) difference of behavior from one
> version to another (2.2 -> 2.4 and more surprisingly from between 
> two 2.4
> versions) is also in question here.
> Even more strange, 2.4 built for other distrib doesn't
> highlight the behaviour !
>
>

 I made another series of test and it seems to be linked to
 fastcgi.

 I took the stock apache (2.4.6 plus tons of patches)  & php-fpm
 (5.4.16 + tons of patches) from RHEL7 and I get the exact same 
 behaviour
 (headers rewritten to EPOCH)
 However, if I server the very same php script from mod_php
 (instead of fcgi) it "works" (the headers are not modified).


>>> For the record, I also have the same behaviour (headers
>>> rewritten when using php-fpm + fastcgi) on alpine linux 3.4 that
>>> ships apache2-2.4.20.
>>> So AFAICT, it doesn't seem distro specific.
>>>
>>> On the root of the problem, from my point of view:
>>> - the difference between mod_php vs. php-fpm + fcgi is
>>> understandable (even if not desired and not documented).
>>> - the fact that fcgi handler parse & rewrite headers seems to
>>> lead to inconsistencies (I'll try to build a test case for that).
>>> - however, even if the headers are wrong, I think apache default
>>> (use EPOCH) is wrong as it leads to very inconsistent behaviour (the
>>> resource will never expire). I would prefer either:
>>> -- do not touch the header
>>> -- raise a warning and discard the header
>>>
>>> What do you think ?
>>>
>>
>>
>> From my tests the following snippet of code should be responsible
>> for the switch from 'foo' to unix epoch:

Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4

[Mike Rumph]

Hello Joe,

You can see the parameters that are available from the WLS plug-ins here:
- 
https://docs.oracle.com/middleware/1213/webtier/PLGWL/plugin_params.htm#PLGWL475


The equivalent to what Yann was referring could be KeepAliveEnabled and 
KeepAliveSecs.
But ConnectTimeoutSecs, ConnectRetrySecs, WLSocketTimeoutSecs and 
WLIOTimeoutSecs might also be useful.


Thanks,

Mike

On 7/1/2016 3:06 AM, Joe Muller wrote:

As far as we can see from fiddler and the Apache logs the request is fully 
sent.   I assume those parameters you mentioned are for mod_proxy ?  We are not 
using mod_proxy for this, we are using the Weblogic plug-in for Apache 2.4.

-Original Message-
From: Yann Ylavic [mailto:ylavic@gmail.com]
Sent: Friday, July 01, 2016 3:42 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 
to Apache 2.4

On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller  wrote:

   One interesting thing we did find on a packet capture on the back end 
between the proxy server and the application server is that 3 seconds after the 
proxy server apparently closed the port, the Weblogic application server tried 
to send data.  It almost like Weblogic did not realize the port was closed.  
Very odd.

Is the HTTP request fully sent (proxy) and responded (backend) when this 
happens? (I try to understand why a backend/application would send data on its 
own).

Otherwise, on a general rule, did you take care that the TTL of proxy 
connection (to the backend) is lower than the KeepAliveTimeout configured on 
the backend?
This can be done by using the ProxyPass/BalancerMember parameter ttl=...
But before that, does disabling keepalive on the proxy help already?
(ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive)

Regards,
Yann.

-
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



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

Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4

[Daniel]

that would certainly be a good test.

To see if you get the same behaviour disabling weblogic plugin and
switching to mod_proxy. If with both the issue happens the same you have a
very good reason to believe the issue is not in the reverse proxy, but
rather the backend or the balancer.

2016-07-01 12:06 GMT+02:00 Joe Muller :

>
> As far as we can see from fiddler and the Apache logs the request is fully
> sent.   I assume those parameters you mentioned are for mod_proxy ?  We are
> not using mod_proxy for this, we are using the Weblogic plug-in for Apache
> 2.4.
>
> -Original Message-
> From: Yann Ylavic [mailto:ylavic@gmail.com]
> Sent: Friday, July 01, 2016 3:42 AM
> To: users@httpd.apache.org
> Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One
> 6.1 to Apache 2.4
>
> On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller  wrote:
> >
> >   One interesting thing we did find on a packet capture on the back end
> between the proxy server and the application server is that 3 seconds after
> the proxy server apparently closed the port, the Weblogic application
> server tried to send data.  It almost like Weblogic did not realize the
> port was closed.  Very odd.
>
> Is the HTTP request fully sent (proxy) and responded (backend) when this
> happens? (I try to understand why a backend/application would send data on
> its own).
>
> Otherwise, on a general rule, did you take care that the TTL of proxy
> connection (to the backend) is lower than the KeepAliveTimeout configured
> on the backend?
> This can be done by using the ProxyPass/BalancerMember parameter ttl=...
> But before that, does disabling keepalive on the proxy help already?
> (ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive)
>
> Regards,
> Yann.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@httpd.apache.org
> For additional commands, e-mail: users-h...@httpd.apache.org
>



-- 
*Daniel Ferradal*
IT Specialist

email dferradal at gmail.com
linkedin es.linkedin.com/in/danielferradal

RE: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4

[Joe Muller]

As far as we can see from fiddler and the Apache logs the request is fully 
sent.   I assume those parameters you mentioned are for mod_proxy ?  We are not 
using mod_proxy for this, we are using the Weblogic plug-in for Apache 2.4.

-Original Message-
From: Yann Ylavic [mailto:ylavic@gmail.com] 
Sent: Friday, July 01, 2016 3:42 AM
To: users@httpd.apache.org
Subject: Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 
to Apache 2.4

On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller  wrote:
>
>   One interesting thing we did find on a packet capture on the back end 
> between the proxy server and the application server is that 3 seconds after 
> the proxy server apparently closed the port, the Weblogic application server 
> tried to send data.  It almost like Weblogic did not realize the port was 
> closed.  Very odd.

Is the HTTP request fully sent (proxy) and responded (backend) when this 
happens? (I try to understand why a backend/application would send data on its 
own).

Otherwise, on a general rule, did you take care that the TTL of proxy 
connection (to the backend) is lower than the KeepAliveTimeout configured on 
the backend?
This can be done by using the ProxyPass/BalancerMember parameter ttl=...
But before that, does disabling keepalive on the proxy help already?
(ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive)

Regards,
Yann.

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

Re: [users@httpd] Issues migrating Weblogic proxies from Sun One 6.1 to Apache 2.4

[Yann Ylavic]

On Fri, Jul 1, 2016 at 12:49 AM, Joe Muller  wrote:
>
>   One interesting thing we did find on a packet capture on the back end 
> between the proxy server and the application server is that 3 seconds after 
> the proxy server apparently closed the port, the Weblogic application server 
> tried to send data.  It almost like Weblogic did not realize the port was 
> closed.  Very odd.

Is the HTTP request fully sent (proxy) and responded (backend) when
this happens? (I try to understand why a backend/application would
send data on its own).

Otherwise, on a general rule, did you take care that the TTL of proxy
connection (to the backend) is lower than the KeepAliveTimeout
configured on the backend?
This can be done by using the ProxyPass/BalancerMember parameter ttl=...
But before that, does disabling keepalive on the proxy help already?
(ProxyPass' disablereuse=on or SetEnv proxy-nokeepalive)

Regards,
Yann.

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