TYPO3 Core

Ive updated the mailinglist:

I've had a look at your approach. I think what you want to do is this:
- Force URLs to be protocol-neutral

What do you mean by protocol-neutral? Relative links?

However, IMHO this makes little sense practically. You seem willing to
define how all URLs (not only some) are requested (HTTP vs. HTTPS),
therefore I don't understand why URLs should still be protocol-neutral
by default.

Im not sure you did understand the problem correctly.

Currently its not possible to have SOME pages with https. Why? Ones a user is using https (forced by url_scheme on a specific page) there is no way to go back to http without > changing the URL manually. Why? Because we need to change the baseUrl of the typoLink calling page to ensure a valid https connection for all resources (not only html but js, > css, pictures, ...).

So IMHO the current implementation of url_scheme is totally useless, as practically you could use https for ALL pages or for NONE (which would be done by baseUrl, no need of > > url_scheme field).
If I am wrong I would love to hear how to use url_scheme in a proper way.

So what I suggest is similar to Jigals suggestion:
If a default scheme is defined (using the new Typoscript setting) then
we automatically enforce all links to be absolute (similar to
forceAbsoluteUrl=1 in Typolink).

Enforcing absoulte urls is what I do in my fix. But not for all links by default, only if needed.

Where should we discuss this? I personally prefer forge as I dont like ml.

It would be awesome to integrate the possibility of a default url_scheme by typoscript in the Core.

Please note there is a (sleeping) mailing list thread for this issue which includes some important info how to improve url_scheme to make it a usable feature. Search for "Scheme enforcement in 4.5.x" in typo3 dev

@Alexander
Perhaps we should discuss there as it has more information and some more members.
I will try to review your changes asap!

It also has some explanation about a possible TypoScript configuration (which is not possible by the way).

Felix Nagel wrote:

Please note there is a (sleeping) mailing list thread for this issue which includes some important info how to improve url_scheme to make it a usable feature. Search for "Scheme enforcement in 4.5.x" in typo3 dev

@Alexander
Perhaps we should discuss there as it has more information and some more members.
I will try to review your changes asap!

It also has some explanation about a possible TypoScript configuration (which is not possible by the way).

I have read the thread you referred to and agree that some form of typoscript is needed to override default behavior, etc. When we've got 100,000+ client pages to deal with it's VERY handy to have some typoscript to handle this. Please can this be on the TODO list for TYPO3 6.x?

I like the "light" version of the patch. Is the discussion on this topic still open?

Hi Felix,

what is the state of this issue?

Considered dead. Perhaps you could try to reactive the mailinglist thread but I guess you will need help of a interested core member to achieve anything... sigh

We are also interested in making this happen. I'll see if I can get a core update submitted (for TYPO3 6+) via Gerritt, and hopefully we can get this moving forward from there.

PS: typo3.org member can submit a change request using the Gerritt system - have a look at http://wiki.typo3.org/Contribution_Walkthrough_with_CommandLine

Hi,

I do not think this is a Bug.

As I understand the url_scheme field I am able to define if a page should be available through
0 = http and https,
1 = only http,
2 = only https

If you like to define a default scheme you could just change the default value für that field in TCA of table pages in typo3conf/ext_tables.php:

$GLOBALS['TCA']['pages']['columns']['url_scheme']['default'] = '1';

Kind Regards
Caspar

It's not a bug, it's a feature request.

Your suggestion is no solution, you want to be able to configure this per part of page tree / per page. (in the BE instead of in code)

Caspar Stuebs wrote:

Hi,

I do not think this is a Bug.

As I understand the url_scheme field I am able to define if a page should be available through
0 = http and https,
1 = only http,
2 = only https

If you like to define a default scheme you could just change the default value für that field in TCA of table pages in typo3conf/ext_tables.php:

$GLOBALS['TCA']['pages']['columns']['url_scheme']['default'] = '1';

Kind Regards
Caspar

There is an error in the TCA syntax:
$GLOBALS['TCA']['pages']['columns']['url_scheme']['config']['default'] = '1';

I'm not sure this really makes sense anymore. The Internet is moving towards https everywhere and TYPO3 even if it should not enforce that, should embrace it and not look back at what would have been useful 4-5 years ago.