Closed hnsr closed 9 months ago
This fixes problems with PURGE requests done by Magento failing, because varnish wasn't actually listening on port 6081 (but on port 80 instead).
Fixed by just mapping 6081 to 80 internally (a better fix would maybe be to make Varnish listen to the correct port, but 80 is fine too.)
Before:
wget --method=PURGE --header="X-Magento-Tags-Pattern: .*" http://127.0.0.1:6081/ --2023-10-06 15:03:58-- http://127.0.0.1:6081/ Connecting to 127.0.0.1:6081... connected. HTTP request sent, awaiting response... No data received. Retrying.
After:
wget --method=PURGE --header="X-Magento-Tags-Pattern: .*" http://127.0.0.1:6081/ --2023-10-06 15:27:06-- http://127.0.0.1:6081/ Connecting to 127.0.0.1:6081... connected. HTTP request sent, awaiting response... 200 Purged Length: 240 [text/html] Saving to: ‘index.html’ index.html 100%[============================================================================================================================>] 240 --.-KB/s in 0s 2023-10-06 15:27:06 (32,7 MB/s) - ‘index.html’ saved [240/240] $ cat index.html <!DOCTYPE html> <html> <head> <title>200 Purged</title> </head> <body> <h1>Error 200 Purged</h1> <p>Purged</p> <h3>Guru Meditation:</h3> <p>XID: 65544</p> <hr> <p>Varnish cache server</p> </body> </html>
:tada: This PR is included in version 3.17.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:
This fixes problems with PURGE requests done by Magento failing, because varnish wasn't actually listening on port 6081 (but on port 80 instead).
Fixed by just mapping 6081 to 80 internally (a better fix would maybe be to make Varnish listen to the correct port, but 80 is fine too.)
Before:
After: