[Pulp-list] Determining a repo from the request URL

[Jay Dobies]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

> Jay, 
> 
> This problem is somewhat related to another issue we saw with relative paths and possible name collisions.  I spoke with dgao about this and he recommended a simple approach which I think will help my issue as well as yours.
> 
> What if we prepend the repo-id to the relative_path, the URL structure becomes:
> https://<host>/<pulp-repo-httpd-location>/<repo-id>/<repo-relative-path>/<requested-file-path>

I like that. A lot. That also avoids the possibility that a user would
nest repos. Nice call dgao.

Let's give it a bit for others to comment, so maybe at the scrum we can
talk about getting someone to pull the trigger on that change.

- -- 
Jay Dobies
RHCE# 805008743336126
Freenode: jdob
http://pulpproject.org
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.14 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJNienNAAoJEOMmcTqOSQHC/9kIAI2tOk3AoZR7td9hvsHDnnQs
alcJyqRJKWZWY8sQYTqzrQp6bwG/ibj8aLvQs9DgIQDiduYsXGBeR+3j2hK+egGO
q44iW86fjbxWFOtwrKaD7RfSL3eYv6FlJEwgWreLOhukE5P9yf0u6VWKQIHOC62x
I+ymhRYsLHXgHrD145ssXFqyQiM3ELUGHzLedwwT9S0LP/X9U8PVeJVScgPtt7di
cUB+JXIkFhSIrlJRMYBorf4U1n3n5hfoJ0pr3V9/VfM9Lem3jxliSCnLMXOC9toF
icXhBGs63oE1mGm2453XUwn0OnVsyiKjToBBL2hYDSkrw3tw2bTlIB1l8V664qw=
=6OuQ
-----END PGP SIGNATURE-----