[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

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



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

On 03/23/2011 10:13 AM, Pradeep Kilambi wrote:
> We store the relative_path for each repo in the model and its unique. So couldn't you do a lookup from the http auth layer to see what repo a given relative path matches and determine access? 

Read my first e-mail. The issue is that I can't figure out the relative
path from the requested URL.

> ~ Prad
> 
> ----- Original Message -----
> From: "John Matthews" <jmatthew redhat com>
> To: "Jay Dobies" <jason dobies redhat com>
> Cc: pulp-list redhat com
> Sent: Wednesday, March 23, 2011 9:06:19 AM
> Subject: Re: [Pulp-list] Determining a repo from the request URL
> 
> 
> 
> ----- Original Message -----
>> -----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?
>>
> 
> I think it'll be done by mid afternoon.  I'll ping you when it's in.
> 
> _______________________________________________
> Pulp-list mailing list
> Pulp-list redhat com
> https://www.redhat.com/mailman/listinfo/pulp-list
> 


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

iQEcBAEBAgAGBQJNigBuAAoJEOMmcTqOSQHCVYsH/RwnO3zFb8VFEGucZH53ifov
buhBMx1Abo3UUsvQD6ZgFuaFrvhMcvwfq54EgUPRbOWrAWc2SK46WmTO8FHObuDM
3ULSuaH3afYXhDzyuJYmJiY27RFycDGbcheUxmDQ8UZE52K+VB5K/Lvgmk5zSBp+
a5z/xNPYDivvqy73tT0TpoNrnKB1Z7hL/jN00cIhwaJ/15lkbH0fKSA/+ach4C2l
wCmFAoajHft+KpNlQpumkSXAzx3Zx2G9a/NfYYQU+ujf4SUHCfDeiAvHtXb06X8+
1x63LfLIALdJ8RIhZ9vfBgvh6XOhyGWJxJgXV/LpgGg9Q42XXHdF6pARVc6SRE0=
=54ZL
-----END PGP SIGNATURE-----


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]