Bug #2557

Links rendered by the Router ignore application context

Added by Robert Lemke almost 11 years ago. Updated about 9 years ago.

Status:
Resolved
Priority:
Must have
Category:
MVC
Start date:
2009-02-04
Due date:
% Done:

100%

PHP Version:
Has patch:
Complexity:

Description

If the application context is != production, the URL usually includes the index_*.php segment:

http://myhost/index_dev.php/foo/bar/baz

The script filename is, however, removed in rendered links which leads to a context switch:

http://myhost/foo/bar/baz

Related issues

Related to TYPO3.Flow - Bug #2751: Routing: generated links must keep index.php if needed Resolved 2009-03-03

Associated revisions

Revision a36605e9 (diff)
Added by Karsten Dambekalns over 10 years ago

FLOW3:
  • the route() method now strips index*.php from the request URI if present, refs #2557
FLOW3, TYPO3v5 & Blog Distributions:
  • adjusted index.php so it uses FLOW3_CONTEXT from environment if set
  • adjusted .htaccess

Revision ee2b88c8 (diff)
Added by Karsten Dambekalns over 10 years ago

FLOW3:
  • the route() method now strips index*.php from the request URI if present, refs #2557
FLOW3, TYPO3v5 & Blog Distributions:
  • adjusted index.php so it uses FLOW3_CONTEXT from environment if set
  • adjusted .htaccess

Revision 4ef766f5 (diff)
Added by Karsten Dambekalns over 10 years ago

FLOW3:
  • the route() method now strips index*.php from the request URI if present, refs #2557
FLOW3, TYPO3v5 & Blog Distributions:
  • adjusted index.php so it uses FLOW3_CONTEXT from environment if set
  • adjusted .htaccess

Revision c1df49a2 (diff)
Added by Karsten Dambekalns over 10 years ago

FLOW3:
  • changed request URI handling, fixes #2557

Revision 49ce65e7 (diff)
Added by Karsten Dambekalns over 10 years ago

FLOW3:
  • changed request URI handling, fixes #2557

History

#1 Updated by Karsten Dambekalns almost 11 years ago

Also the routing has hard-coded support only for index_dev.php, other contexts are not supported.

It would be nice to switch the context depending on an environment variable, this would be very useful for CLI calls. And Apache can set the environment variable as part of a rewrite rule, so that FLOW3 never sees the "URL-encoding" of the context. Hm, something like that.

#2 Updated by Karsten Dambekalns over 10 years ago

  • Status changed from New to Accepted
  • Assignee set to Karsten Dambekalns

#3 Updated by Karsten Dambekalns over 10 years ago

  • Status changed from Accepted to Resolved
  • % Done changed from 0 to 100

Applied in changeset r1967.

Also available in: Atom PDF