Project

General

Profile

Actions

Bug #21852

closed

PageNotFound_handling works incorrectly

Added by Thomas Lange almost 15 years ago. Updated about 11 years ago.

Status:
Rejected
Priority:
Won't have this time
Assignee:
-
Category:
Frontend
Target version:
-
Start date:
2009-12-13
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
4.3
PHP Version:
5.2
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

When using
- default TYPO3 .htaccess file
- without 'simulate static documents' and
- without any additional extensions
that 404 pagenotfound_handling works only for requested files/URL's in form: ".../index.php?id=2":

If page with id=2 exists, then this page will shown.
If page with id=2 doesn't exist, then the correct message "Error, The page did not exist..." will shown.
So far so good.

2 Problems:

1.) www.domain.com.de/wrongfile.html or www.domain.com.au/wrongfile.htm shows the page with id=0 (homepage, startpage), if the isn't any wrongfile. That's not correctly.
Also If I set the PageNotFound_handling in the InstallTool every time I get the page with id=0.

2.) E.g. a page with id=2 exists, then

- www.domain.com.de/index.php?id=2 is correctly.

The following examples should show the message "Error, The page did not exist...", but
they show also the Page with id=2:

- www.domain.com.de/ind.php?id=2
- www.domain.com.de/wrongfile.html?id=2
- www.domain.com.de/?id=2

I have only checked this with TYPO3 4.3.0.

In the bugreport #0008343 for older TYPO3-versions I can find a similar discussion,
but not the same failure results.

When I use RealURL it appears PageNotFound_handling works correctly.

(issue imported from #M13025)


Related issues 1 (0 open1 closed)

Related to TYPO3 Core - Bug #18754: improved 404 pagenotfound_handling not working for certain requested URLs/resourcesClosed2008-05-06

Actions
Actions #1

Updated by Alexander Opitz about 11 years ago

  • Category deleted (Communication)
  • Status changed from New to Needs Feedback
  • Target version deleted (0)
  • Is Regression set to No

Hi,

as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?

Actions #2

Updated by Ernesto Baschny about 11 years ago

  • Category set to Frontend
  • Status changed from Needs Feedback to Rejected
  • Priority changed from Should have to Won't have this time

The problem here is that you don't want to enable rewriting if you are not using any URL rewriting extension. So just turn off the RewriteRule in your .htaccess file.

Default _.htaccess contains this comment:

# You need rewriting, if you use a URL-Rewriting extension (RealURL, CoolUri).

expecting that most people uses some of these extensions. If you don't, don't rewrite everything to index.php. So I don't consider this a bug of TYPO3 to be solved.

Actions

Also available in: Atom PDF