Skip to content

Conversation

@Yspadadden
Copy link
Contributor

resolves #61

Given a Guzzle client with a base uri like
http://example.com/myregistryliveshere/.

Requests where created with a relative path with a leading /.
Guzzle interprets this as a path from the root and replaces
/myregistryliveshere/ with the given path.

To make Guzzle combine the path correctly with the given
base_uri, the relative path must not start with a /. Then
it is appended at the end of the base_uri, preserving the
path in the base_uri.

Mario Eberhard and others added 2 commits July 29, 2021 07:59
resolves flix-tech#61

Given a Guzzle client with a base uri like
`http://example.com/myregistryliveshere/`.

Requests where created with a relative path with a leading `/`.
Guzzle interprets this as a path from the root and replaces
`/myregistryliveshere/` with the given path.

To make Guzzle combine the path correctly with the given
base_uri, the relative path must not start with a `/`. Then
it is appended at the end of the base_uri, preserving the
path in the base_uri.
@tPl0ch
Copy link
Collaborator

tPl0ch commented Aug 11, 2021

@Yspadadden unfortunately the test cases for the requests are now failing. Would you be able to update the test cases to reflect the changes?

@Yspadadden
Copy link
Contributor Author

I will give it a shot. PHP is not my strong suit. But the failing tests seem fixable.

tPl0ch and others added 3 commits August 11, 2021 10:24
After removing the leading "/" from the requests the unit tests
failed, because they still expected the leading "/". So removed
this from the tests as well to match the code in Functions
again.
@tPl0ch tPl0ch merged commit d9c4dec into flix-tech:master Aug 12, 2021
@tPl0ch
Copy link
Collaborator

tPl0ch commented Aug 12, 2021

@Yspadadden thanks for your contribution, much appreciated! I will try to release this fix asap.

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

Successfully merging this pull request may close these issues.

Support registries not hosted at root

2 participants