Getting old buffer + header + correct response
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
apache2 (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
UBUNTU RELEASE
Description: Ubuntu 16.04.3 LTS
Release: 16.04
APACHE2 VERSION
apache2:
Installed: 2.4.18-2ubuntu3.14
Candidate: 2.4.18-2ubuntu3.14
Version table:
*** 2.4.18-2ubuntu3.14 500
500 http://
100 /var/lib/
2.
500 http://
2.
500 http://
WHAT I EXPECT TO HAPPEN
That a correct response is sent back, see below.
WHAT ACTUALLY HAPPENS
We have apache2 as a reverse proxy server, doing a lot of things: 4 Virtual Hosts, several RewriteRules, SSL to a non-SSL internal (Domino) server, quite some ProxyPass* lines, and a few Substitutes to fix links in returned HTML.
In 98% of all cases everything works, only, in 2% of the page requests the browser gets the wrong response: it contains the homepage html, then the header for the actual response, and then the correct response.
Here an extract of the middle part of the returned response, where two buffers seem to be joined:
-------
XSP.addOnLoad(
XSP.attachEvent
XSP.attachEvent
XSP.attachEvent
});
</script>
</body>
</html>HTTP/1.1 200 OK
Date: Fri, 24 Apr 2020 22:03:21 GMT
Content-Type: text/html;
Expires: -1
Content-Length: 72703
<!DOCTYPE html>
<html lang="en">
<head>
<base href="/
<title>
<link rel="SHORTCUT ICON" href="/
<meta name="viewport" content=
<link rel="stylesheet" href="https:/
<meta name="Description" content="info">
<link rel="stylesheet" type="text/css" href="/
-------
The output comes from one single line in the Firefox 75.0 Developer Tools window, on the Network tab.
The same happens every now and then on a page that regularly refreshes an image on the screen. Usually (98%) the response is correct, but sometimes two responses are combined into one and then the browser flips.
Needless to say maybe, but if I access the website directly, i.e. not through the proxy server, there's no problem whatsoever, the response is always correct.
Thank you for looking into this. If you need more info, please contact me by mail.
Changed in apache2 (Ubuntu): | |
status: | Incomplete → New |
Hello Sjef,
Thank you for taking the time to file a bug report.
Would you mind providing more information about your issue ?
1) Have you tried the same with a more recent apache/ubuntu combination ?
2) Have you tried the latest 20.04 LTS with the same configuration ? Does it face this issue ?
3) Could you provide a specific step-by-step reproducer for your issue ?
Since there is not enough information in your report to begin triage or to
differentiate between a local configuration problem and a bug in Ubuntu, I
am marking this bug as "Incomplete". We would be grateful if you would:
provide a more complete description of the problem, explain why you
believe this is a bug in Ubuntu rather than a problem specific to your
system, and then change the bug status back to "New".
For local configuration issues, you can find assistance here: www.ubuntu. com/support/ community
http://