Allow external hosts to request the proxy #8

Closed
TheSophiaDev wants to merge 4 commits from allow-external-hosts into main
TheSophiaDev commented 2025-05-14 10:15:39 +02:00 (Migrated from github.com)

In the case that a headless installation of TYPO3 is used, there are often different domains for the TYPO3 backend and frontend.In this scenario the referrer does not match the host. In order to still allow the frontend to use the proxy, I have added a configuration of additional allowed domains. This means that anyone can allow additional domains to use the proxy in the future.

Can this please also be published as a new version of v1.2.8 so that it can still be used for TYPO3 v11.5?

In the case that a headless installation of TYPO3 is used, there are often different domains for the TYPO3 backend and frontend.In this scenario the referrer does not match the host. In order to still allow the frontend to use the proxy, I have added a configuration of additional allowed domains. This means that anyone can allow additional domains to use the proxy in the future. Can this please also be published as a new version of v1.2.8 so that it can still be used for TYPO3 v11.5?
trokohl commented 2025-05-14 12:25:10 +02:00 (Migrated from github.com)

The individual API endpoints already have settings in themselves, so I would not make this option global for all of them.
I think it should be in the FlexForm of the page settings.

If I simply overwrite version 1.2.8, I cannot get it updated at https://extensions.typo3.org/extension/tile_proxy. I should create a new 1.2.9.

The individual API endpoints already have settings in themselves, so I would not make this option global for all of them. I think it should be in the FlexForm of the page settings. If I simply overwrite version 1.2.8, I cannot get it updated at https://extensions.typo3.org/extension/tile_proxy. I should create a new 1.2.9.
TheSophiaDev commented 2025-05-14 13:27:43 +02:00 (Migrated from github.com)

Hello,
I can see the advantages of maintenance in FlexForms. However, these domains differ depending on the environment. For example, there is a big difference between the test system and the production system in terms of the domain. With the FlexForm it would be in the database, which does not allow sync between the systems. It can easily be passed as an environment variable via the GLOBALS.
Do you have a suggestion to address both challenges?

I also meant version 1.2.9, which in turn needs 1.2.8 as a basis and unfortunately there was no branch to put the PR there.

Hello, I can see the advantages of maintenance in FlexForms. However, these domains differ depending on the environment. For example, there is a big difference between the test system and the production system in terms of the domain. With the FlexForm it would be in the database, which does not allow sync between the systems. It can easily be passed as an environment variable via the GLOBALS. Do you have a suggestion to address both challenges? I also meant version 1.2.9, which in turn needs 1.2.8 as a basis and unfortunately there was no branch to put the PR there.
trokohl commented 2025-05-14 13:32:34 +02:00 (Migrated from github.com)

well, a fallback solution is posible.

=> If not in FlexForm then take from global settings.

and yes that's right, I should create the branch, but I didn't expect further development for 11 ;-)

well, a fallback solution is posible. => If not in FlexForm then take from global settings. and yes that's right, I should create the branch, but I didn't expect further development for 11 ;-)
TheSophiaDev commented 2025-05-14 13:37:50 +02:00 (Migrated from github.com)

That's a very good idea. I will implement it and then, when the branch for 11.5 exists, open the PR for the branch as well.

Yes, I understand that. :)

That's a very good idea. I will implement it and then, when the branch for 11.5 exists, open the PR for the branch as well. Yes, I understand that. :)
trokohl commented 2025-05-14 13:49:33 +02:00 (Migrated from github.com)

There is now a TYPO3-11 branch

There is now a TYPO3-11 branch

Pull request closed

Sign in to join this conversation.
No description provided.