Skip to content
This repository was archived by the owner on May 6, 2026. It is now read-only.

Allow external hosts to request the proxy#8

Closed
TheSophiaDev wants to merge 4 commits into
codemacherUG:mainfrom
TheSophiaDev:allow-external-hosts
Closed

Allow external hosts to request the proxy#8
TheSophiaDev wants to merge 4 commits into
codemacherUG:mainfrom
TheSophiaDev:allow-external-hosts

Conversation

@TheSophiaDev
Copy link
Copy Markdown

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
Copy link
Copy Markdown
Contributor

trokohl commented May 14, 2025

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
Copy link
Copy Markdown
Author

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
Copy link
Copy Markdown
Contributor

trokohl commented May 14, 2025

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
Copy link
Copy Markdown
Author

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
Copy link
Copy Markdown
Contributor

trokohl commented May 14, 2025

There is now a TYPO3-11 branch

@trokohl trokohl closed this May 15, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants