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

Jay Dobies jason.dobies at redhat.com
Wed Mar 23 12:46:03 UTC 2011


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

>>> 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'd be happy to make the change, will wait till after Scrum to let others provide feedback.

Rock. How long do you think it will take? Would you be start it right
away or do you have anything else on your plate in the way?

It's kinda critical for me to be able to finish up the repo auth stuff.
Part of waiting until the scrum was going to be to find a resource, but
since you volunteered I'm not sure it makes sense to wait on it. You and
Prad are most familiar with that area, so can you run it by him to see
if anything is glaringly wrong with it and start on it earlier?

- -- 
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/

iQEcBAEBAgAGBQJNieuLAAoJEOMmcTqOSQHCgkAH/3+YcT7f+yKwBmijSIuyWCT5
2CErJ7Lg+QaWIVGJGoioNUDzJ09QBC2xcCholcTXE5ixqMK8UL3mL9D4yLWbsRk7
XnrybJynPb9Vlkft/8wwyAsZav9dCeS9vQerw6QOSQoYNwnghsIINZvHzsrB8wZE
RLWxcrT9BAPo3KhCQwDm7Y/HvsLGLxC6Su7BXST8xRcYTDSFSgD7cQg/8slrAqpc
eklo1ILjVI2vvgfyF9SABR8IFE5IJGn0pbcVOduw/gf7UeDRVmYovKP+uGuxnqbn
BcU2amP+BJqMr01cv4VF7agGkAY0ovypo/lNJBGr0+SJlRZkjhqk7EoHvjtKmq4=
=eVo1
-----END PGP SIGNATURE-----




More information about the Pulp-list mailing list