[TYPO3-core] RFC: pageNotFound_handling HTTP status fix
Dmitry Dulepov
dima at spamcop.net
Mon Apr 24 15:04:01 CEST 2006
Hi!
Martin Kutschker wrote:
>>> Why is FOLLOWLOCATION used here and not in t3lib_div::getURL().
> You didn't answer that one, but after reading the docs I think it
> should be used in t3lib_div::getURL.
I really did not know why it is not used in t3lib_div. May be, there was
a reason. In case of 404 page, redirect or not - is insignificant, we
always need a "final" page, which is retrieved with correct UA and
referer. I think you are right, t3lib_div should have this flag as well.
But t3lib_div's function cannot have the same referer and UA
automatically because it url in that function ius not fetched by client
directly. It can be fetched by a plugin and client may never know or see
it (for example, it can be a payment system, or code generator page).
So, this is different from 404 page. This is why I really had to make
extra function.
I though about making additional parameter but decided to avoid it for
two reasons:
- it is not common use case for t3lib_div's function to have such
functionality
- I can pass array there but I will have to parse it and use differently
for fopen and cUrl, which complicates things.
Thus having a separate dedicated function was the best solution in my
opinion.
Of course, I can be wrong. What I am sure about is that this bug (with
404) should be finally fixed.
Dmitry.
--
"It is our choices, that show what we truly are,
far more than our abilities." (A.P.W.B.D.)
More information about the TYPO3-team-core
mailing list