-
Notifications
You must be signed in to change notification settings - Fork 29
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
Pulp 2 and 3 API calls through Apache don't play nice #49
Closed
Comments
wbclark
added a commit
to wbclark/puppet-pulp
that referenced
this issue
Dec 13, 2019
This is to resolve theforeman/puppet-pulpcore#49
wbclark
added a commit
to wbclark/puppet-pulpcore
that referenced
this issue
Dec 13, 2019
Merged
wbclark
added a commit
to wbclark/puppet-pulp
that referenced
this issue
Dec 14, 2019
This is to resolve theforeman/puppet-pulpcore#49
wbclark
added a commit
to wbclark/puppet-pulp
that referenced
this issue
Dec 14, 2019
This is to resolve theforeman/puppet-pulpcore#49
ehelms
pushed a commit
to theforeman/puppet-pulp
that referenced
this issue
Dec 16, 2019
This is to resolve theforeman/puppet-pulpcore#49
cegeka-jenkins
pushed a commit
to cegeka/puppet-pulpcore
that referenced
this issue
Aug 9, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What worked for me locally:
move pulp.conf to 10-pulp.conf so it loads after foreman vhost (https://github.com/theforeman/puppet-pulp/blob/master/manifests/apache.pp#L128)
move pulpcore.conf proxy to /pulp/api/v3 instead of just /pulp/api that way it tries to match there first and falls back to Pulp 2 URLs
The text was updated successfully, but these errors were encountered: