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
I'm currently using Flask-WTF v0.13.1, i have a few forms on my website, all created including the CSRF token.
For some reasons i have to set a different expiration on each form, so far i could set manually the time_limit value upon creating the csrf token.
I would like to update to the v0.14, according to the changelogtime_limit is gone and there is no reference in the docs on how to change it anymore.
Looking in the source code i saw that the form has a csrf_time_limit meta parameter.
I tried to set that parameter on my form:
from flask_wtf import FlaskForm
class myForm(FlaskForm):
class Meta:
csrf_time_limit = 7200
content = TextAreaField('content')
Although debugging the csrf.pymodule i see that the validate_csrf_token of _FlaskFormCSRF is actually never called.
The method validate_csrf is called within the method protect() instead, in this case the meta parameter is never considered.
I don't understand if this is a bug of the package or if i'm missing something.
The text was updated successfully, but these errors were encountered:
I'm currently using Flask-WTF v0.13.1, i have a few forms on my website, all created including the CSRF token.
For some reasons i have to set a different expiration on each form, so far i could set manually the
time_limit
value upon creating the csrf token.I would like to update to the v0.14, according to the changelog
time_limit
is gone and there is no reference in the docs on how to change it anymore.Looking in the source code i saw that the form has a
csrf_time_limit
meta parameter.I tried to set that parameter on my form:
Although debugging the
csrf.py
module i see that thevalidate_csrf_token
of_FlaskFormCSRF
is actually never called.The method
validate_csrf
is called within the methodprotect()
instead, in this case the meta parameter is never considered.I don't understand if this is a bug of the package or if i'm missing something.
The text was updated successfully, but these errors were encountered: