Bug #36004

Wrong HTTP protocol in combination with a proxy

Added by Michael Staatz about 1 year ago. Updated 8 months ago.

Status:Closed Start date:2012-04-13
Priority:Should have Due date:
Assignee:- % Done:

100%

Category:-
Target version:-
TYPO3 Version:4.6 Complexity:
PHP Version:
Votes: 0

Description

When a reverse proxy is configured in $TYPO3_CONF_VARS and you call
t3lib_div::getIndpEnv('TYPO3_SSL') it returns the wrong protocol.

You can reproduce this in the following way:
If realUrl has the configuration to take the next higher level in the page tree in the case of not finding the current page
then the protocol will be changed by the static method t3lib_div::getIndpEnv('TYPO3_SSL')

Example:

http://url-zur-seite/die-es nicht-gibt

results

https://url-zur-seite

Associated revisions

Revision 2b40a5e2
Added by Michael Staatz about 1 year ago

[BUGFIX] Wrong HTTP protocol in combination with a proxy

When a reverse proxy is configured in $TYPO3_CONF_VARS and you call
t3lib_div::getIndpEnv('TYPO3_SSL') it returns the wrong protocol.

You can reproduce this in the following way:
If realUrl has the configuration to take the next higher level in the
page tree in the case of not finding the current page then the protocol
will be changed by the static method t3lib_div::getIndpEnv('TYPO3_SSL')

Change-Id: I7a3c74c117753edfc1b9552d4110479f3a013f46
Fixes: #36004
Releases: 4.7, 4.6, 4.5
Reviewed-on: http://review.typo3.org/10433
Reviewed-by: Sebastian Popovic
Tested-by: Sebastian Popovic
Reviewed-by: Tom Ruether
Tested-by: Tom Ruether
Reviewed-by: Chris Wittmann
Tested-by: Chris Wittmann
Reviewed-by: Tolleiv Nietsch
Tested-by: Tolleiv Nietsch

Revision 126fb5ea
Added by Michael Staatz about 1 year ago

[BUGFIX] Wrong HTTP protocol in combination with a proxy

When a reverse proxy is configured in $TYPO3_CONF_VARS and you call
t3lib_div::getIndpEnv('TYPO3_SSL') it returns the wrong protocol.

You can reproduce this in the following way:
If realUrl has the configuration to take the next higher level in the
page tree in the case of not finding the current page then the protocol
will be changed by the static method t3lib_div::getIndpEnv('TYPO3_SSL')

Change-Id: I6fdf61df8597fb84b822fa840475182643b0b134
Fixes: #36004
Releases: 4.7, 4.6, 4.5
Reviewed-on: http://review.typo3.org/10685
Reviewed-by: Michael Staatz
Tested-by: Michael Staatz
Reviewed-by: Stefan Neufeind
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Revision 8be224b7
Added by Michael Staatz about 1 year ago

[BUGFIX] Wrong HTTP protocol in combination with a proxy

When a reverse proxy is configured in $TYPO3_CONF_VARS and you call
t3lib_div::getIndpEnv('TYPO3_SSL') it returns the wrong protocol.

You can reproduce this in the following way:
If realUrl has the configuration to take the next higher level in the
page tree in the case of not finding the current page then the protocol
will be changed by the static method t3lib_div::getIndpEnv('TYPO3_SSL')

Change-Id: I40817be254a330e9d083cf45ccb25500571ebc4b
Fixes: #36004
Releases: 4.7, 4.6, 4.5
Reviewed-on: http://review.typo3.org/10684
Reviewed-by: Michael Staatz
Tested-by: Michael Staatz
Reviewed-by: Stefan Neufeind
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Revision e3c17a02
Added by Michael Staatz about 1 year ago

[BUGFIX] Wrong HTTP protocol in combination with a proxy

When a reverse proxy is configured in $TYPO3_CONF_VARS and you call
t3lib_div::getIndpEnv('TYPO3_SSL') it returns the wrong protocol.

You can reproduce this in the following way:
If realUrl has the configuration to take the next higher level in the
page tree in the case of not finding the current page then the protocol
will be changed by the static method t3lib_div::getIndpEnv('TYPO3_SSL')

Change-Id: I7a3c74c117753edfc1b9552d4110479f3a013f46
Fixes: #36004
Releases: 4.7, 4.6, 4.5
Reviewed-on: http://review.typo3.org/10683
Reviewed-by: Michael Staatz
Tested-by: Michael Staatz
Reviewed-by: Stefan Neufeind
Reviewed-by: Christian Kuhn
Tested-by: Christian Kuhn

Revision 1a6c495f
Added by Michael Staatz about 1 year ago

[BUGFIX] Wrong HTTP protocol in combination with a proxy

When a reverse proxy is configured in $TYPO3_CONF_VARS and you call
t3lib_div::getIndpEnv('TYPO3_SSL') it returns the wrong protocol.

You can reproduce this in the following way:
If realUrl has the configuration to take the next higher level in the
page tree in the case of not finding the current page then the protocol
will be changed by the static method t3lib_div::getIndpEnv('TYPO3_SSL')

Change-Id: I7a3c74c117753edfc1b9552d4110479f3a013f46
Fixes: #36004
Releases: 4.7, 4.6, 4.5
Reviewed-on: http://review.typo3.org/10433
Reviewed-by: Sebastian Popovic
Tested-by: Sebastian Popovic
Reviewed-by: Tom Ruether
Tested-by: Tom Ruether
Reviewed-by: Chris Wittmann
Tested-by: Chris Wittmann
Reviewed-by: Tolleiv Nietsch
Tested-by: Tolleiv Nietsch

History

Updated by Gerrit Code Review about 1 year ago

  • Status changed from New to Under Review

Patch set 1 for branch master has been pushed to the review server.
It is available at http://review.typo3.org/10433

Updated by Gerrit Code Review about 1 year ago

Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at http://review.typo3.org/10683

Updated by Gerrit Code Review about 1 year ago

Patch set 1 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/10684

Updated by Gerrit Code Review about 1 year ago

Patch set 1 for branch TYPO3_4-5 has been pushed to the review server.
It is available at http://review.typo3.org/10685

Updated by Michael Staatz about 1 year ago

  • Status changed from Under Review to Resolved
  • % Done changed from 0 to 100

Updated by Gerrit Code Review 10 months ago

  • Status changed from Resolved to Under Review

Patch set 1 for branch TYPO3_4-7 has been pushed to the review server.
It is available at http://review.typo3.org/13120

Updated by Gerrit Code Review 10 months ago

Patch set 1 for branch TYPO3_4-6 has been pushed to the review server.
It is available at http://review.typo3.org/13242

Updated by Wouter Wolters 8 months ago

Please close this issue. All affected branches are up to date.

Updated by Stefan Galinski 8 months ago

  • Status changed from Under Review to Closed

Also available in: Atom PDF