TYPO3 Core

Can you please explain your setup in more detail?

The Server sends status 301 and redirects to the configured login page

What is the configuration you're using here?

I can confirm this behaviour. Whenever a frontend user tries to navigate to an access restricted page but is not logged in, a 301 redirect is happening to login page. After logging in, trying to navigate to the initial page will result in a cached redirect by the browser. The suggested patch works but it is maybe not the optimal way. We are using TYPO3 6.1.5 with Realurl on a fairly standard LAMP server.

What is your Typoscript setup to achieve the redirect to the login form?

The code mentioned resides in the checkPageForShortcutRedirect() function? If so, I'm a bit unsure what a shortcut has to do with felogin redirect.

I think the redirect happens because of this Realurl configuration: 'postVarSet_failureMode'=>'redirect_goodUpperDir'. And I was wondering too how the shortcut function is related, but it fixed the situation. Is the original author using Realurl too?

Are all points cleared out so that this issue can be closed?

Hi Alexander

I think I have to clarify the issue.

Let's have a look at the following page structure:

|- parent page (shortcut mode first subpage)
  |- page 1 (restricted to group 1)
  |- page 2 (restricted to group 2)
  |- Login (public)
  |- common page (restricted to groups 1 and 2)

When an anonymous user access the common page TYPO3 issues a permanent redirect to the Login page. This should be changed to "302 Found".

Our setup us as follows:

• TYPO3 4.7.19
• Realurl 1.12.7
• no postVarSet_failureMode set

Thank you
Andreas

What happens if you disable realurl?
Is it the same with TYPO3 CMS 6.2?

301 is not good in most cases, but we've to figure out which component is triggering it, the Core or realurl

1. RealURL does not handle anything regarding authentication or login because it runs before the page id is known to TYPO3. Without page id it is not possible to redirect anywhere.
2. RealURL does not handle anything regarding permissions to view pages. It only decodes/encodes URLs given to it. It is up to the caller to handle the rest.
3. RealURL always uses a custom HTTP status line to let you know that it is redirected. A typical RealURL redirect produces the following status line: HTTP/1.0 301 TYPO3 RealURL redirect

So the chance that it is RealURL is 0.001%.

Thanks Dmitry for clarification!!

What happens if you disable realurl?

The problem persists with config.tx_realurl_enable=0

Is it the same with TYPO3 CMS 6.2?

I haven't tried this setup with 6.2 yet.

301 is not good in most cases, but we've to figure out which component is triggering it, the Core or realurl

I think it's the core becaus my patch of typo3/sysext/cms/tslib/class.tslib_fe.php worked for me an the status code is harcoded there in line 2.788.

Andreas

I will close the issue, if you agree.

Of course you may close this issue. Great that it is fixed in 6.2.

Thank you
Andreas