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
Setting the forceEncoding option on this filter not only forces the encoding on the request, but also on the response itself, which is rather agressive and can lead to issues like described in #18698.
Adding a new setForceResponseEncoding option should allow to selectively force the encoding on the request only. Of course, this option should be set to true by default for backwards compatibility.
Brian Clozel opened SPR-14240 and commented
Setting the
forceEncoding
option on this filter not only forces the encoding on the request, but also on the response itself, which is rather agressive and can lead to issues like described in #18698.Adding a new
setForceResponseEncoding
option should allow to selectively force the encoding on the request only. Of course, this option should be set totrue
by default for backwards compatibility.Referenced from: commits 05b29a4, 76ee468
The text was updated successfully, but these errors were encountered: