Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

strange behaviour when frontend called by GeneralUtility::getUrl #61

Open
nabossha opened this issue Dec 21, 2016 · 2 comments
Open

strange behaviour when frontend called by GeneralUtility::getUrl #61

nabossha opened this issue Dec 21, 2016 · 2 comments

Comments

@nabossha
Copy link

I encounter a strange behaviour using coolURI 1.1.3 on TYPO3 7.6.x (multiple installations and versions tested):

the Extension cs_seo uses the function "GeneralUtility::getUrl" to load the frontend-page and analyse it's content. when coolURI is active, it logs the following behaviour on devlog.
when GeneralUtility::getUrl is called with this url: http://dev.abc.local/index.php?id=103 - the following gets logged:

SITESCRIPT: /index.php?id=103
Getting domain for 103
Looking for domain on page 103
Looking for domain on page 4
Looking for domain on page 1
Resolved domain: dev.abc.local
URL from cache 2: dev.abc.local@downloads/
SITESCRIPT: /dev.abc.local/downloads/
DOMAIN: dev.abc.local

as you can see, the domain "dev.abc.local" gets suddenly prepended to the URL itself - this behaviour just occurs when called via backend - page requests in the frontend work as expected.
the IP of these log-entries are always the server's IP itself, not the IP from the logged-in backend-user. i suspect there may be something going on with redirects/session-variables which may not be present when called with getURL?

I tried tracing the error down in several coolURI functions but had no luck - what may be the cause of this error?

@bednee
Copy link
Owner

bednee commented Dec 21, 2016 via email

@nabossha
Copy link
Author

nabossha commented Dec 22, 2016

disabling "redirectOldLinksToNew" solves the problem but i think that's not an ideal solution since there is possibility of duplicate content (but "canonical"-TAG is set so this should be a minor issue). i still don't get it why the domain gets prepended to the URL-path itself

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants