Ralf Claussnitzer

Any progress on this? I'm stuck with the issue. Can't seem to hack a workaround.

I see, you're right. The devlog is filled with "severe" errors. It also contains a message about this problem. However, I might have overlooked it because of its label: `[tx_dlf_document->load(http://localhost:8000/index...`...

There are even more places, where more detailed error reporting could be used: ``` $ grep -R 'GeneralUtility::getUrl(' plugins/pageview/class.tx_dlf_geturl_eid.php: $fetchedHeader = GeneralUtility::getUrl($url, 2); plugins/pageview/class.tx_dlf_geturl_eid.php: $fetchedData = GeneralUtility::getUrl($url, $includeHeader); plugins/pageview/class.tx_dlf_geturl_eid.php: $fetchedHeader...

Not sure. These codes seem so have very particular focus. 502 Bad Gateway: "The server, while acting as a gateway or proxy, received an invalid response from the upstream server...

That is indeed true. Also if the given URL is rubbish the response code could be `400 Bad Request`.

You are right. On the first look this issue is some kind of a mixed bag. Problem no.1 being double encoding and problem no.2 identifier resolving. I think I meant...

Another problem with URLs as identifiers popped up: The given URL has to be resolvable by the TYPO3 system running the extension. In case of Docker containers with port mapping...

So there is a `location` URL parameter? The problem is that this URL needs to be resolvable from within the TYPO3 runtime. This is not necessarily the case in Docker...

@pzygielo As far as I understand the given command executes an explicit goal not bound to a lifecycle phase. What did you expect instead?

This is a strange bug. Ampersands in the query component are implemented. This is the output on my machine, running Java 8: ``` urn:XY:ORDER:111111?=x=y&z=c ``` What Java version are you...