On Tue, Aug 01, 2017 at 06:21:21PM -0700, Kevin Fenzi wrote: > On 08/01/2017 01:44 PM, Randy Barlow wrote: > > On Tue, 2017-08-01 at 22:23 +0200, Pierre-Yves Chibon wrote: > >> But, do we want to follow the same path in production or do we want > >> to deploy it > >> at src.fp.o/ directly? > > > > I like src.fpo.o aesthetically, but don't have a technical argument one > > way or the other. > > I like putting it at / but we do have some stuff at /lookaside/ and > /cgit (going away?). So I suppose best might be redirecting / to /pagure > and dropping cgit? So I looked at this this morning, we can put pagure in / and keep /lookaside (and even /cgit) working cf: https://src.stg.fedoraproject.org/lookaside https://src.stg.fedoraproject.org/cgit https://src.stg.fedoraproject.org/ The issue is with this last one, we have in our apache conf: RedirectMatch permanent ^/$ https://src.fedoraproject.org/cgit/ (also in stg, so stg redirects to prod there, but it works, using curl you'll get the pagure page) So, how long does it take for a browser to forget about a 301 code? I think we can break the look by introducing an infinite loop that will make the force the browser to recheck the original 301 but that means putting a redirect from cgit to pagure which effectively answers the question of whether we want to drop cgit or not. If we move the redirect from / to /pagure we will face the same 301 redirect issue that the browser has cached. More ideas/thoughts? Pierre
Attachment:
signature.asc
Description: PGP signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
