https://bz.apache.org/bugzilla/show_bug.cgi?id=61999
--- Comment #6 from Michael ---
(In reply to Remy Maucherat from comment #5)
> A fix will be in 9.0.4, 8.5.25, 8.0.49 and 7.0.84.
Great, thank you!
With this fix our request won't fail anymore for maxSavePostSize=0. And for
maxSavePostSize >
https://bz.apache.org/bugzilla/show_bug.cgi?id=61999
Remy Maucherat changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://bz.apache.org/bugzilla/show_bug.cgi?id=61999
--- Comment #4 from Remy Maucherat ---
"Furthermore the current implementation behaves as follows:
* value < 0 means no limit
* value >= 0 means limited to the value => so for value=0 every request with
any POST data will fail (403 Forbidden)"
https://bz.apache.org/bugzilla/show_bug.cgi?id=61999
--- Comment #3 from Michael ---
BTW: We are willing to provide a patch if you agree.
--
You are receiving this mail because:
You are the assignee for the bug.
-
To unsubscrib
https://bz.apache.org/bugzilla/show_bug.cgi?id=61999
--- Comment #2 from Michael ---
Thanks for your fast reply. Yes we have an actual need to disable the "save
post data" feature during authentication. We do not want the request to fail
(with 403) just because the POST data was more than x KB si
https://bz.apache.org/bugzilla/show_bug.cgi?id=61999
--- Comment #1 from Remy Maucherat ---
Ok, so the documentation isn't implemented properly when it comes to 0. Do you
have an actual need to disable the feature, or is this one of these academic
bug reports ? I'm asking since disabling the feat
https://bz.apache.org/bugzilla/show_bug.cgi?id=61999
Michael changed:
What|Removed |Added
CC||bsi@gmail.com
--
You are receiving this
