Bug 2037967
| Summary: | Apache reverse proxy doesn't seem to handle websockets correctly | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Linux 8 | Reporter: | Verhoeckx <j.verhoeckx> | ||||||
| Component: | httpd | Assignee: | Luboš Uhliarik <luhliari> | ||||||
| Status: | CLOSED WONTFIX | QA Contact: | rhel-cs-infra-services-qe <rhel-cs-infra-services-qe> | ||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 8.5 | CC: | luhliari | ||||||
| Target Milestone: | rc | Flags: | j.verhoeckx:
needinfo?
(luhliari) j.verhoeckx: needinfo? (luhliari) |
||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | --- | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2023-07-06 07:28:06 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Attachments: |
|
||||||||
|
Description
Verhoeckx
2022-01-06 22:07:41 UTC
Created attachment 1849355 [details]
Diagram of the software setup
The complete documentation of my setup can be found here: https://jeroenverhoeckx.com/build-your-own-online-ide.html I don't write this bug report in order to solve my problem, but I sincerely believe that it's a more general problem. Let me know if there something that I could do to help solve this possible bug! And if it's not a bug, I also would like to hear it (and hopefully find a workaround)! Will this problem be solved in RHEL 8.6? How can I get attention for the bug report? After evaluating this issue, there are no plans to address it further or fix it in an upcoming release. Therefore, it is being closed. If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened. |