Actions
Task #3697
closedStory #3693: Lazy for Pulp3
Have Pulp do a simple redirect (no signing) to squid when the content app needs to serve a RemoteArtifact
Status:
CLOSED - CURRENTRELEASE
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:
100%
Estimated time:
Platform Release:
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Sprint:
Sprint 41
Quarter:
Description
When the content app finds only a RemoteArtifact, it needs to issue a Redirect to the user. Specifically it needs to redirect to:
{protocol_handler}{redirect_host}:{redirect_port}/{redirect_prefix_path}/{the path to the content the user requested just now}
So if the protocol handler is https://, redirect_host=example.com, redirect_port=443, and redirect_prefix_path = /squid/ then a request came to the content app like:
https://mypulpserver.com/pulp/api/v3/content/path/to/distribution/subpath/to/content/
The redirect would be:
https://example.com/squid/pulp/api/v3/content/path/to/distribution/subpath/to/content/
Related issues
Updated by dkliban@redhat.com over 6 years ago
- Groomed changed from No to Yes
- Sprint Candidate changed from No to Yes
Updated by jortel@redhat.com over 6 years ago
- Status changed from NEW to ASSIGNED
- Assignee set to jortel@redhat.com
Updated by dkliban@redhat.com over 6 years ago
- Blocked by Task #3696: Add the streamer's settings to settings.yaml in the content app area added
Updated by jortel@redhat.com over 6 years ago
- Status changed from ASSIGNED to POST
Added by jortel@redhat.com over 6 years ago
Added by jortel@redhat.com over 6 years ago
Updated by jortel@redhat.com over 6 years ago
- Status changed from POST to MODIFIED
- % Done changed from 0 to 100
Applied in changeset pulp|c35bba60db1d10f7420cd4108b7a960ca073d122.
Updated by bmbouter almost 5 years ago
- Status changed from MODIFIED to CLOSED - CURRENTRELEASE
Actions
Support redirect in the content application. closes #3696, #3697