Mailing List Archive: Apache, anyone?

Apache, anyone?

Sep 25, 2006, 10:15 AM

Post #1 of 5 (2608 views)

Lennart Regebro wrote:
> Personally, I don't care where www.zope.org is currently located, and
> I also think we should replace it part by part with microsites, like
> wiki.zope.org, bugs.zope.org, news.zope.org, products.zope.org and so
> on,

Be careful the multiple domain names, it prevents sensible cookie-based
auth. For that reason alone, I'd prefer to see zope.org/wiki,
zope.org/bugs, zope.org/news, etc instead.

It really feels like we need a foundation-admin'ed Apache in front of
everything somewhere, just to handle rewriting/static content/etc. Is
that a possiblity?

cheers,

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk

_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Re: Apache, anyone? [ In reply to ]

regebro at gmail

Sep 25, 2006, 11:19 AM

Post #2 of 5 (2549 views)

Permalink

On 9/25/06, Chris Withers <chris@simplistix.co.uk> wrote:
> Be careful the multiple domain names, it prevents sensible cookie-based
> auth. For that reason alone, I'd prefer to see zope.org/wiki,
> zope.org/bugs, zope.org/news, etc instead.

Can't you set the cookie for just zope.org? That's what I'm doing on a
project right now, and that works fine...
--
Lennart Regebro, Nuxeo http://www.nuxeo.com/
CPS Content Management http://www.cps-project.org/
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Re: Apache, anyone? [ In reply to ]

justizin at siggraph

Sep 25, 2006, 11:27 AM

Post #3 of 5 (2533 views)

Permalink

On 9/25/06, Chris Withers <chris@simplistix.co.uk> wrote:
> Lennart Regebro wrote:
> > Personally, I don't care where www.zope.org is currently located, and
> > I also think we should replace it part by part with microsites, like
> > wiki.zope.org, bugs.zope.org, news.zope.org, products.zope.org and so
> > on,
>
> Be careful the multiple domain names, it prevents sensible cookie-based
> auth. For that reason alone, I'd prefer to see zope.org/wiki,
> zope.org/bugs, zope.org/news, etc instead.

Isn't it possible to set a cookie for ".zope.org" vs, say, "www.zope.org" ?

I'm pretty sure I know some people doing this at:

http://linklink.timesys.com +
http://builder.timesys.com

and also:

http://www.fsf.org/ +
http://wiki.fsf.org/

> It really feels like we need a foundation-admin'ed Apache in front of
> everything somewhere, just to handle rewriting/static content/etc. Is
> that a possiblity?

I own a lot of Apaches already, I would not mind.

--
Justizin, Independent Interactivity Architect
ACM SIGGRAPH SysMgr, Reporter
http://www.siggraph.org/
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Re: Re: Apache, anyone? [ In reply to ]

chris at simplistix

Sep 26, 2006, 3:01 AM

Post #4 of 5 (2540 views)

Permalink

Lennart Regebro wrote:
> On 9/25/06, Chris Withers <chris@simplistix.co.uk> wrote:
>> Be careful the multiple domain names, it prevents sensible cookie-based
>> auth. For that reason alone, I'd prefer to see zope.org/wiki,
>> zope.org/bugs, zope.org/news, etc instead.
>
> Can't you set the cookie for just zope.org? That's what I'm doing on a
> project right now, and that works fine...

Cool, didn't know that worked :-)

Does it work in all the major browsers?

Chris

--
Simplistix - Content Management, Zope & Python Consulting
- http://www.simplistix.co.uk
_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web

Re: Apache, anyone? [ In reply to ]

faassen at infrae

Sep 26, 2006, 5:42 AM

Post #5 of 5 (2534 views)

Permalink

Chris Withers wrote:
> Lennart Regebro wrote:
>> Personally, I don't care where www.zope.org is currently located, and
>> I also think we should replace it part by part with microsites, like
>> wiki.zope.org, bugs.zope.org, news.zope.org, products.zope.org and so
>> on,
>
> Be careful the multiple domain names, it prevents sensible cookie-based
> auth. For that reason alone, I'd prefer to see zope.org/wiki,
> zope.org/bugs, zope.org/news, etc instead.

Good point, though it depends on whether we want authentication. I
imagine we do want that in case with the wiki.

> It really feels like we need a foundation-admin'ed Apache in front of
> everything somewhere, just to handle rewriting/static content/etc. Is
> that a possiblity?

I want to move in that direction, but it's not a near-term possibility.
We can rewire things inside of Squid though if we asked overworked ZC
admins nicely..

Regards,

Martijn

_______________________________________________
Zope-web maillist - Zope-web@zope.org
http://mail.zope.org/mailman/listinfo/zope-web