Bug #90155
closed
Wrong status code with message "Unable to determine path to entry script."
0%
Description
If i call a URL like https://www.baseUrl.com/index.php/ab/cd/ there is an error 500 with the message "Unable to determine path to entry script." thrown.
The message is okay for me, but the status code 500 says that it is an "internal server error" witch is not really right.
The error code should be in the 400er range, 400, 404, what ever. But it's really no server error (which security tests like "penetration tests" recognize).
Updated by Benni Mack over 4 years ago
- Status changed from New to Needs Feedback
IMHO this is correct. A 500 means that the server says "I did something worng", whereas 400 means "you (= client) did something wrong". The status code clearly stems from the fact that TYPO3 was configured inproperly, not that the user has accessed a non-reachable URL.
I guess you're running Apache2 with PATH_INFO set up?
Updated by Tobias Kummer over 4 years ago
Benni Mack wrote:
IMHO this is correct. A 500 means that the server says "I did something worng", whereas 400 means "you (= client) did something wrong". The status code clearly stems from the fact that TYPO3 was configured inproperly, not that the user has accessed a non-reachable URL.
I guess you're running Apache2 with PATH_INFO set up?
Yes, I'm running Apache2 with most probably PATH_INFO (don't know exactly).
I have a plain TYPO3 with a default site-configuration. That would say: TYPO3 is configured wrong per default, isn't it?
Do you have a configuration for TYPO3 or server for make this misbehaviour running?
Updated by Anja Leichsenring over 2 years ago
is this behaviour still an issue in supported versions? As far as I understand there should never be a index.php included in the resulting URL.
I will close the issue if no actions happens until end of may 2022.
Updated by Stefan Bürk over 2 years ago
- Related to Bug #97543: Correctly resolve instance script path added
Updated by Stefan Bürk over 2 years ago
Should be fixed with #97543 at least for v10/11 and main
Updated by Riccardo De Contardi about 2 years ago
- Status changed from Needs Feedback to Closed
- Target version deleted (
next-patchlevel)
No feedback since 5 months => closing this issue.
If you think that this is the wrong decision or experience the issue again and have more information about how to reproduce your problem, please reopen it or open a new issue with a reference to this one.
Thank you and best regards