Project

Profile

Help

Task #3866

Document how to serve http vs https content

Added by jsherril@redhat.com over 1 year ago. Updated 6 months ago.

Status:
MODIFIED
Priority:
Normal
Assignee:
Category:
-
Sprint/Milestone:
Start date:
Due date:
% Done:

100%

Platform Release:
Blocks Release:
Backwards Incompatible:
No
Groomed:
Yes
Sprint Candidate:
Yes
Tags:
Documentation, Easy Fix, Katello-P1
QA Contact:
Complexity:
Smash Test:
Verified:
No
Verification Required:
No
Sprint:
Sprint 44

Description

Document how users can serve content over both http and https using Pulp and a webserver. This involves having two prefixes (e.g. /http/.../ and /https/.../) for distribution base paths. Then the user sets up the webserver (nginx or apache or whatever) to server the content over http or https based on this prefix.


Related issues

Duplicated by Pulp - Story #3662: Add docs on how to support enabling http vs https for certain publications CLOSED - DUPLICATE Actions

Associated revisions

Revision d7a289a3 View on GitHub
Added by daviddavis about 1 year ago

Documenting how to serve http and https content

fixes #3866
https://pulp.plan.io/issues/3866

Revision d7a289a3 View on GitHub
Added by daviddavis about 1 year ago

Documenting how to serve http and https content

fixes #3866
https://pulp.plan.io/issues/3866

Revision d7a289a3 View on GitHub
Added by daviddavis about 1 year ago

Documenting how to serve http and https content

fixes #3866
https://pulp.plan.io/issues/3866

History

#1 Updated by daviddavis over 1 year ago

  • Tracker changed from Issue to Task
  • % Done set to 0

#2 Updated by daviddavis over 1 year ago

  • Sprint/Milestone set to 3.0

#3 Updated by daviddavis about 1 year ago

I think the last thing we decided on was to have two prefixes (e.g. /http/.../ and /https/.../) for distribution base paths. Then setting up the webserver (nginx or apache or whatever) to server the content over http or https based on this prefix. This is supported now and would just require some documentation.

I'm wondering if this is still the route we want to go?

#4 Updated by bmbouter about 1 year ago

@daviddavis I think something like that is the only technical route I know of because Pulp can't be sure that http connections aren't actually being served via https instead. A path convention like this allows coordination between the sysadmin installing Pulp and the user using Pulp. +1 to documenting the convention as you've described it.

It's effectively a documentation-only feature since Pulp provides no special handling in this area. I like that because it allows environments which don't need both types (all https for example) to not have to think about it.

#5 Updated by daviddavis about 1 year ago

  • Subject changed from Document or provide a mechanism for serving http vs https content to Document how to serve http vs https content
  • Description updated (diff)
  • Tags Documentation added
  • Tags deleted (Katello-P1)

#6 Updated by bmbouter about 1 year ago

  • Groomed changed from No to Yes
  • Sprint Candidate changed from No to Yes

Thanks @daviddavis. Yes, this looks right to me.

#7 Updated by dkliban@redhat.com about 1 year ago

  • Sprint set to Sprint 41
  • Tags Easy Fix, Katello-P1 added

#8 Updated by daviddavis about 1 year ago

  • Duplicated by Story #3662: Add docs on how to support enabling http vs https for certain publications added

#9 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 41 to Sprint 42

#10 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 42 to Sprint 43

#11 Updated by rchan about 1 year ago

  • Sprint changed from Sprint 43 to Sprint 44

#12 Updated by daviddavis about 1 year ago

  • Status changed from NEW to POST
  • Assignee set to daviddavis

#13 Updated by daviddavis about 1 year ago

  • Status changed from POST to MODIFIED
  • % Done changed from 0 to 100

#14 Updated by bmbouter 6 months ago

  • Tags deleted (Pulp 3)

Please register to edit this issue

Also available in: Atom PDF