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

[Pradeep Kilambi]

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? 

~ Prad

----- Original Message -----
From: "John Matthews" <jmatthew at redhat.com>
To: "Jay Dobies" <jason.dobies at redhat.com>
Cc: pulp-list at 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 at redhat.com
https://www.redhat.com/mailman/listinfo/pulp-list

-- 
 
-- 
Pradeep Kilambi | irc: prad
Red Hat Systems Management
Phone: +1 919 754 4285
RHCE/RHCDS # 805008680430554