Issue #8870: Unpublished content can be accessed if relative path of content is know - Pulp

Actions

Send by e-mail Copy link

Issue #8870

closed

Unpublished content can be accessed if relative path of content is know

Added by dalley almost 3 years ago. Updated over 2 years ago.

Status:

CLOSED - CURRENTRELEASE

Priority:

Normal

Assignee:

gerrod

Category:

Sprint/Milestone:

3.15.0

Start date:

Due date:

Estimated time:

Severity:

2. Medium

Version:

Platform Release:

OS:

Triaged:

Yes

Groomed:

Sprint Candidate:

Tags:

Sprint:

Sprint 102

Quarter:

Description

It is expected for the package to be available at http://pulp3-source-centos7/pulp/content/fixture/Packages/b/bear-4.1-1.noarch.rpm

It is not expected for the package to be available at http://pulp3-source-centos7/pulp/content/fixture/bear-4.1-1.noarch.rpm (the root of the repo)

Neither primary.xml nor the directory listing show the files in the repo root, although they are that way in the original repo.

To reproduce:

pulp rpm remote create --name=fixture --url=https://fixtures.pulpproject.org/rpm-unsigned/ --policy=on_demand
pulp rpm repository create --name=fixture --remote=fixture
pulp rpm repository sync --name fixture
pulp rpm publication create --repository fixture
pulp rpm distribution create --name fixture --repository fixture --base-path=fixture

Files

Screenshot from 2021-06-04 15-30-44.png (180 KB) Screenshot from 2021-06-04 15-30-44.png

dalley, 06/04/2021 09:34 PM

Related issues

Actions

Copy link

Updated by dalley almost 3 years ago

None of the repodata files are available from the root.

Actions

Copy link

Updated by dkliban@redhat.com almost 3 years ago

Project changed from Pulp to RPM Support

Actions

Copy link

Updated by dalley almost 3 years ago

Priority changed from Normal to Low
Triaged changed from No to Yes

Actions

Copy link

Updated by dalley almost 3 years ago

Project changed from RPM Support to Pulp

Actions

Copy link

Updated by gerrod almost 3 years ago

Subject changed from Packages which weren't published at the repository root are available at the repository root to Unpublished content can be accessed if relative path of content is know
Assignee set to gerrod
Priority changed from Low to Normal

This problem affects all publication based plugins. Steps to reproduce

Create repo: pulp file repository create --name test
Create remote: pulp file remote create --name test --url https://fixtures.pulpproject/file/PULP_MANIFEST
Sync repo: pulp file repository sync --name test --remote test
Create distribution: pulp file distribution create --name test --base-path test --repository test
Access unpublished content: http :24816/pulp/content/test/1.iso
Get 404 for published metadata: http :24816/pulp/content/test/PULP_MANIFEST