Project

General

Profile

Actions

Task #88755

closed

Remove POST option from typolink.addQueryString

Added by Oliver Hader over 4 years ago. Updated over 4 years ago.

Status:
Closed
Priority:
Should have
Assignee:
-
Category:
Link Handling, Site Handling & Routing
Target version:
-
Start date:
2019-07-15
Due date:
% Done:

100%

Estimated time:
TYPO3 Version:
10
PHP Version:
Tags:
Complexity:
Sprint Focus:

Description

Setting addQueryString.method of typolink could be used like shown below in order to transform HTTP POST parameters into according GET parameters.

    typolink {
        parameter = 123
        addQueryString = 1
        addQueryString.method = POST
    }

In terms of correctly using HTTP verbs it's bad practise in general to treat GET and POST equally, besides that documentation already mentioned potential side-effects like accidentally exposing sensitive data submitted via POST to proxies or log files.

That's why values POST, GET,POST and POST,GET are not allowed anymore for typolink.addQueryString.method. Maintaining functionality - if required at all - has to be done using domain specific logic in according controllers or middleware implementations.

The POST feature has been introduced before TYPO3 v4.0 already, GET,POST and POST,GET were introduced for TYPO3 v4.1 with #16859 in 6537dd5c4806419f74e92a4b4855b2a2c108a621


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Feature #16859: typolink.addQueryString: Enable usage of merged POST and GET data by new TypoScript configurationClosedOliver Hader2007-01-16

Actions
Actions

Also available in: Atom PDF