You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Pound assumes the RewriteLocation setting to be 1 by default. That default dates back to the days of version 2.8. However, due to the bug in RewriteLocation implementation, it wasn't actually working until the bug was fixed in version 4.13. It appears, however, that the fix brought quite some hassle for existing installations, which relied on RewriteLocation 0 behavior without requesting it explicitly (e.g. this issue). I must admit that my servers were affected as well :) That being said, I'm considering changing the default to 0, that is: no rewriting of Location and Content-Location headers.
Do you agree with pound assuming `RewriteLocation 0` as default?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Pound assumes the RewriteLocation setting to be 1 by default. That default dates back to the days of version 2.8. However, due to the bug in
RewriteLocationimplementation, it wasn't actually working until the bug was fixed in version 4.13. It appears, however, that the fix brought quite some hassle for existing installations, which relied onRewriteLocation 0behavior without requesting it explicitly (e.g. this issue). I must admit that my servers were affected as well :) That being said, I'm considering changing the default to 0, that is: no rewriting ofLocationandContent-Locationheaders.0 votes ·
All reactions