验证:有人看到过 apache2 响应两个响应和一个标头吗?

验证:有人看到过 apache2 响应两个响应和一个标头吗?

我已经在 launchpad.net 和 BugZilla 上提交了错误报告,但我想确认是否有人遇到过此问题。我们使用 apache2 作为客户网站的反向代理服务器。有时,虽然是随机的,但在所有请求的 2% 中,我们得到的不是正常的响应内容,而是一种双重响应:响应 A,然后是响应 B 的标头,然后是响应 B。这非常烦人,因为网站对客户非常重要,而一个无法正常运行的网站可能会吓跑用户。

如果我们直接访问 Web 服务器,即不使用代理服务器,则完全没有问题。

我可以在这里重复整个故事(并且当被要求时我会这样做),但我希望错误报告的链接就足够了:https://bugs.launchpad.net/ubuntu/+source/apache2/+bug/1874932

当我以为这是 Web 服务器上的编程问题时,StackOverflow 上的原始问题如下:https://stackoverflow.com/questions/61304769/xpages-server-sends-wrong-data-apache2-problem

再次,我的问题是:有人熟悉这种现象吗?如果是的话,有快速解决方法吗?或者我们应该选择不同的反向代理服务器?

感谢您的帮助!

更新

error.log 文件的一部分,用于每分钟刷新一次的页面。前两段是正确的,第三段导致错误,第四段又是正确的。希望这能给你一些线索……

[Sun Apr 26 12:09:22.769237 2020] [ssl:info] [pid 2797:tid 139815423543040] [client 12.34.56.789:40606] AH01964: Connection to child 64 established (server www.website.com:443)
[Sun Apr 26 12:09:23.012497 2020] [ssl:info] [pid 2797:tid 139815278311168] [client 12.34.56.789:40608] AH01964: Connection to child 73 established (server www.website.com:443)
[Sun Apr 26 12:09:23.552035 2020] [proxy:debug] [pid 2797:tid 139815423543040] mod_proxy.c(1161): [client 12.34.56.789:40606] AH01143: Running scheme http handler (attempt 0), referer: https://www.website.com/__Test__
[Sun Apr 26 12:09:23.552080 2020] [proxy:debug] [pid 2797:tid 139815423543040] proxy_util.c(2210): [client 12.34.56.789:40606] AH00944: connecting http://www.website.com:81/database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__
[Sun Apr 26 12:09:23.552090 2020] [proxy:debug] [pid 2797:tid 139815423543040] proxy_util.c(2419): [client 12.34.56.789:40606] AH00947: connected /database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__

[Sun Apr 26 12:10:22.701472 2020] [ssl:info] [pid 2796:tid 139815202776832] [client 12.34.56.789:40616] AH01964: Connection to child 18 established (server www.website.com:443)
[Sun Apr 26 12:10:22.953876 2020] [ssl:info] [pid 2796:tid 139815320274688] [client 12.34.56.789:40624] AH01964: Connection to child 4 established (server www.website.com:443)
[Sun Apr 26 12:10:23.442074 2020] [proxy:debug] [pid 2796:tid 139815202776832] mod_proxy.c(1161): [client 12.34.56.789:40616] AH01143: Running scheme http handler (attempt 0), referer: https://www.website.com/__Test__
[Sun Apr 26 12:10:23.442138 2020] [proxy:debug] [pid 2796:tid 139815202776832] proxy_util.c(2210): [client 12.34.56.789:40616] AH00944: connecting http://www.website.com:81/database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__
[Sun Apr 26 12:10:23.442153 2020] [proxy:debug] [pid 2796:tid 139815202776832] proxy_util.c(2419): [client 12.34.56.789:40616] AH00947: connected /database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__

[Sun Apr 26 12:11:21.443567 2020] [ssl:info] [pid 2796:tid 139815244740352] [client 12.34.56.789:40644] AH01964: Connection to child 13 established (server www.website.com:443)
[Sun Apr 26 12:11:21.534754 2020] [proxy:debug] [pid 2796:tid 139815244740352] mod_proxy.c(1161): [client 12.34.56.789:40644] AH01143: Running scheme http handler (attempt 0), referer: https://www.website.com/__Test__
[Sun Apr 26 12:11:21.534798 2020] [proxy:debug] [pid 2796:tid 139815244740352] proxy_util.c(2210): [client 12.34.56.789:40644] AH00944: connecting http://www.website.com:81/database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__
[Sun Apr 26 12:11:21.534804 2020] [proxy:debug] [pid 2796:tid 139815244740352] proxy_util.c(2419): [client 12.34.56.789:40644] AH00947: connected /database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__
[Sun Apr 26 12:12:22.627945 2020] [ssl:info] [pid 2797:tid 139815219562240] [client 12.34.56.789:40658] AH01964: Connection to child 80 established (server www.website.com:443)
[Sun Apr 26 12:12:22.872992 2020] [ssl:info] [pid 2797:tid 139815227954944] [client 12.34.56.789:40660] AH01964: Connection to child 79 established (server www.website.com:443)
[Sun Apr 26 12:12:23.303433 2020] [proxy:debug] [pid 2797:tid 139815219562240] mod_proxy.c(1161): [client 12.34.56.789:40658] AH01143: Running scheme http handler (attempt 0), referer: https://www.website.com/__Test__
[Sun Apr 26 12:12:23.303488 2020] [proxy:debug] [pid 2797:tid 139815219562240] proxy_util.c(2210): [client 12.34.56.789:40658] AH00944: connecting http://www.website.com:81/database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__
[Sun Apr 26 12:12:23.303496 2020] [proxy:debug] [pid 2797:tid 139815219562240] proxy_util.c(2419): [client 12.34.56.789:40658] AH00947: connected /database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__

[Sun Apr 26 12:13:21.524116 2020] [ssl:info] [pid 2796:tid 139815286703872] [client 12.34.56.789:40672] AH01964: Connection to child 8 established (server www.website.com:443)
[Sun Apr 26 12:13:21.817112 2020] [ssl:info] [pid 2796:tid 139815345452800] [client 12.34.56.789:40674] AH01964: Connection to child 1 established (server www.website.com:443)
[Sun Apr 26 12:13:22.121726 2020] [proxy:debug] [pid 2796:tid 139815286703872] mod_proxy.c(1161): [client 12.34.56.789:40672] AH01143: Running scheme http handler (attempt 0), referer: https://www.website.com/__Test__
[Sun Apr 26 12:13:22.121779 2020] [proxy:debug] [pid 2796:tid 139815286703872] proxy_util.c(2210): [client 12.34.56.789:40672] AH00944: connecting http://www.website.com:81/database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__
[Sun Apr 26 12:13:22.121785 2020] [proxy:debug] [pid 2796:tid 139815286703872] proxy_util.c(2419): [client 12.34.56.789:40672] AH00947: connected /database.nsf/Page.xsp/Page?$$ajaxid=view%3A_id1%3A_id2%3A_id3%3A_id47%3A_id48%3A0%3A_id49%3A_id51%3AtblMemory&$$viewid=!3fa81zwu176jh8r7dcutv7eff! to www.website.com:81, referer: https://www.website.com/__Test__

答案1

很遗憾,这个问题现在已经“解决”了,因为我们准备切换到 nginx……我们遇到了一些问题,但不是上面讨论的溢出问题。当然,这个错误仍然存​​在于 Apache 中。

相关内容