Skip to content
  • Alexander Schnitzler's avatar
    [BUGFIX] Use ForwardResponse arguments if not null · b6c2a5ea
    Alexander Schnitzler authored and Christian Kuhn's avatar Christian Kuhn committed
    
    
    Issue #92815 introduced a regression which triggered an endless
    recursion in case of a validation error.
    
    A bit longer explanation:
    
    Given there is an extbase controller action with an argument
    whose properties have to validated, extbase maps the incoming
    data of the request onto the internally handled arguments
    object which then performs the validation on all given arguments.
    
    In case of an error, extbase tries to redirect to the referring
    request aka the current request with an updated set of arguments.
    The idea is to remove all arguments of the current request to not
    trigger the same validation error again on the next try.
    
    There was a condition in the past which eventually led to the
    overriding of current arguments which was refactored wrong.
    
    The solution is to make the arguments of the ForwardResponse null
    by default and have the same null check like before.
    
    Releases: master
    Resolves: #94457
    Change-Id: I1701001ce0cf55df79b2ed896d69a08659a2902b
    Reviewed-on: https://review.typo3.org/c/Packages/TYPO3.CMS/+/70020
    Tested-by: default avatarcore-ci <typo3@b13.com>
    Tested-by: default avatarwaldhacker <hello@waldhacker.dev>
    Tested-by: default avatarOliver Bartsch <bo@cedev.de>
    Tested-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
    Reviewed-by: default avatarwaldhacker <hello@waldhacker.dev>
    Reviewed-by: default avatarOliver Bartsch <bo@cedev.de>
    Reviewed-by: default avatarChristian Kuhn <lolli@schwarzbu.ch>
    b6c2a5ea