Re: XHTML vs. HTML4 and csrf middleware in particular

2006-10-17 Thread Antonio Cavedoni
On 17 Oct 2006, at 12:21, Michael Radziej wrote: > Antonio, you're probably suffering from a severe read-only-first- > paragraph syndrome here. Proposed cure is to read email again until > bottom hits ;-) Michael: you’re right, I’m a moron :-) Sorry for wasting everyone’s time. Cheers. -- A

Re: XHTML vs. HTML4 and csrf middleware in particular

2006-10-17 Thread James Bennett
On 10/17/06, Michael Radziej <[EMAIL PROTECTED]> wrote: > What is the current policy? Should this output be xhtml conform > or not? Policy for Django? There isn't one, so far as I know. Policy for the web in general? Good luck with that :) > The point is, and that goes above the csrf message, I

Re: XHTML vs. HTML4 and csrf middleware in particular

2006-10-17 Thread Michael Radziej
Antonio Cavedoni schrieb: > Hi Michael, > > On 17 Oct 2006, at 12:00, Michael Radziej wrote: >> Large part of Django seems to use xhtml, and I like it somehow >> better than html, so I use it and give to browsers that accept it >> application/xhtml+xml as media type (and to others I feed the

Re: XHTML vs. HTML4 and csrf middleware in particular

2006-10-17 Thread Antonio Cavedoni
Hi Michael, On 17 Oct 2006, at 12:00, Michael Radziej wrote: > Large part of Django seems to use xhtml, and I like it somehow > better than html, so I use it and give to browsers that accept it > application/xhtml+xml as media type (and to others I feed the same > input but call it text/htm

XHTML vs. HTML4 and csrf middleware in particular

2006-10-17 Thread Michael Radziej
Hi, I have to start with a little background. There's the still interesting issue of what media type you give to your pages and whether to use html4 or xhtml. Large part of Django seems to use xhtml, and I like it somehow better than html, so I use it and give to browsers that accept it appl