Bug #24642
closedpages with Enforce Protocol(SSL) generate false URL
0%
Description
I installed typo3 4.5 in an alias of my domain name (Not directly at the root of my domain name) :
http://www.domain-name.com/alias/
When I set https in the Enforce Protocol select list typo3 generate a bad link.
Example with typolink :
page.11 = TEXT
page.11.value = TEst
page.11.typolink{
parameter=9
}
Typo3 generate :
https://www.domain-name.com/index.php?id=9
instead of :
https://www.domain-name.com/alias/index.php?id=9
(issue imported from #M17118)
Files
Updated by Michel MAIER almost 14 years ago
I think it's a new feature of typo3 core, in 4.4 it's necessary to install a specific extension like dmc_https.
Updated by Jigal van Hemert almost 14 years ago
17118_JvH.patch is a patch for trunk which tries to use the correct path if config.absRefPrefix is not set.
absRefPrefix could be used in this case to have absolute URLs to the right directory, but it would indeed be nice if it would work without further configuration.
Updated by Michel MAIER almost 14 years ago
I tried the patch, it's work... but the '/' after the alias is doubled like that
https://www.domain-name.com/alias//index.php?id=9
Updated by Michel MAIER almost 14 years ago
I noted an other problem, when I am on an https page, all links become relatives.
Set config.baseURL to https://www.domain-name.com/alias/ isn't a solution because all not enforced links become https..
Updated by Ernesto Baschny almost 14 years ago
Any solution in sight, Susanne? Does Jigal's fix work for you?
Updated by Ernesto Baschny almost 14 years ago
Is this an issue still? if so, please consider reviewing the proposed solutions and ultimately get it into the core list for reviews. So that we can have that fixed in 4.5.x sometime.
Thanks!
Updated by Steffen Gebert almost 14 years ago
I think there's no working solution, yet.
Updated by Steffen Ritter almost 14 years ago
Hello Michael,
thanks Ernesto for pointing me out to this one with your open Todo list.
As I implemented this feature, I will take care :)
First, I think, all links are relative by default if absolute is not forced, and the domain is not changed. Therefore your (Michael, 24.11.) seems not to be a bug to me.
As I just enhanced the "linkAcrossDomain" feature a little bit, I think, this is a bug, even without https when linking across domains.
I will inform you about my investigations. So far I cannot tell, as I had not had a deeper look at it.
Updated by Jigal van Hemert almost 14 years ago
17118_JvH_V2.patch is against current trunk and fixes the trailing slash.
The relative URLs are correct; there are three options for the option 'Use protocol':
- Default: keep current protocol
- http:// : force http
- https:// : force https
When I set https:// for a page links to that page are absolute with https protocol. All links to other pages with 'Default' are relative, because they will use the current protocol. On that same page a link to a page with protocol http:// is absolute and forces the http:// protocol.
AFAIK can tell this is intended behaviour and the patch fixes the problem with the directories in the path.
Updated by Steffen Ritter almost 14 years ago
attached patch is on core list..
@Michel Maier, if you mind to vote if this works for you, we could go ahead
Updated by Klaus Storch over 13 years ago
Hello Steffen (Ritter),
I had some problems with the related bug about cross domain- and cross protocol-links. Honestly I didn't actually try your patch - but from looking at it, I'm rather sure your patch will break cross domain links. Before setting $targetDomain to $currentDomain, you need to check wether it's a cross domain link.
Updated by Oliver Hader over 13 years ago
- Target version changed from 4.5.1 to 4.5.6
Updated by Christian Ludwig about 13 years ago
Hi Jigal and Steffen,
In the notice 11 is described that the setting "Default" will keep the protocol.
Great would be a TS Config parameter that would control the ‘Default’ so you don't have e.g. to set every page except one to http:
Simply changing config.baseURL or config.absRefPrefix to http:... does not help because several browsers will show a warning that some content (like images javascript, ...) is delivered insecure.
So I would expect that ‘Default’ switches the protocol to a default setting that is set to http by default and that could be changed by TS. A setting that leaves the protocol as is seems bootless to me, but if there is any need for it, a fourth option should be added.
Updated by Chris topher about 13 years ago
- Target version changed from 4.5.6 to 4.5.8
Updated by Ernesto Baschny almost 13 years ago
- Target version changed from 4.5.8 to 4.5.12
Updated by Steffen Ritter almost 13 years ago
- Status changed from Accepted to Needs Feedback
I think this does not apply anymore due to the recent fixes?
Could you please give feedback on that?
Updated by Navi over 12 years ago
Yes the feature of setting a default protocol is still very much needed.
Updated by Christian Ludwig over 12 years ago
Yes, a default like in notice 15 is strongly needed. Thanks.
Updated by Alexander Opitz about 11 years ago
Hi,
as this issue is very old. Does the problem still exists within newer versions of TYPO3 CMS (4.5 or 6.1)?
Updated by Alexander Opitz almost 11 years ago
- Status changed from Needs Feedback to Closed
- Assignee deleted (
Steffen Ritter) - Target version deleted (
4.5.12) - Is Regression set to No
No feedback within the last 90 days => closing this ticket.
If you think that this is the wrong decision or experience this issue again, then please write to the mailing list typo3.teams.bugs with issue number and an explanation or open a new ticket and add a relation to this ticket number.