On Fri, 2009-04-17 at 09:37 +1000, Graham Dumpleton wrote:
> >> I am not sure we ended up with a final answer on all of this, but I
> >> don't want to hold up mod_wsgi 3.0, which includes Python 3.0 support,
> >> any longer. As such, am implementing things as per:
> >>
> >> http://www.wsgi.org/ws
2009/4/17 Robert Brewer :
> On Thu, 2009-04-16 at 00:12 -0700, Graham Dumpleton wrote:
>> > So, from where I sit, we have:
>> >
>> > 1. Many header values which are ASCII.
>> > 2. A few header values which are ISO-8859-1 plus RFC 2047.
>> > 3. A few header values which are URI's (no specified en
On Fri, Apr 17, 2009 at 02:03, Graham Dumpleton
wrote:
> 2009/4/17 James Y Knight :
>> On Apr 16, 2009, at 3:12 AM, Graham Dumpleton wrote:
>>>
>>> I am not sure we ended up with a final answer on all of this, but I
>>> don't want to hold up mod_wsgi 3.0, which includes Python 3.0 support,
>>> any
2009/4/17 James Y Knight :
> On Apr 16, 2009, at 3:12 AM, Graham Dumpleton wrote:
>>
>> I am not sure we ended up with a final answer on all of this, but I
>> don't want to hold up mod_wsgi 3.0, which includes Python 3.0 support,
>> any longer. As such, am implementing things as per:
>>
>> http://
On Apr 16, 2009, at 3:12 AM, Graham Dumpleton wrote:
I am not sure we ended up with a final answer on all of this, but I
don't want to hold up mod_wsgi 3.0, which includes Python 3.0 support,
any longer. As such, am implementing things as per:
http://www.wsgi.org/wsgi/Amendments_1.0
with excep
On Thu, 2009-04-16 at 00:12 -0700, Graham Dumpleton wrote:
> > So, from where I sit, we have:
> >
> > 1. Many header values which are ASCII.
> > 2. A few header values which are ISO-8859-1 plus RFC 2047.
> > 3. A few header values which are URI's (no specified encoding) or
> IRI's
> > (UTF-8).
>
2009/4/4 Robert Brewer :
> Alan Kennedy wrote:
>> [Bill]
>> > I think the controlling reference here is RFC 3875.
>>
>> I think the controlling references are RFC 2616, RFC 2396 and RFC
> 3987.
>>
>> RFC 2616, the HTTP 1.1 spec, punts on the question of character
>> encoding for the request URI.
>>