Oct 4, 2012 at 12:51 PM, Julian Cerruti
> <jcer...@willowgarage.com
> > wrote:
>
>> Apparently the current implementation of URLField rejects Web Sockets
>> URLs such as ws://my.server.com/
>>
>> This seems to be due to the implementation of the underlying
On Fri, Oct 5, 2012 at 12:51 AM, Julian Cerruti
<jcerr...@willowgarage.com> wrote:
> Apparently the current implementation of URLField rejects Web Sockets URLs
> such as ws://my.server.com/
>
> This seems to be due to the implementation of the underlying URLValidator,
> which
code base and modify/use
accordingly.
I'm not sure on the best way to make proposals. Hopefully someone else can
chime in there for you.
On Thu, Oct 4, 2012 at 12:51 PM, Julian Cerruti
<jcerr...@willowgarage.com>wrote:
> Apparently the current implementation of URLField rejects Web Soc
Apparently the current implementation of URLField rejects Web Sockets URLs
such as ws://my.server.com/
This seems to be due to the implementation of the underlying URLValidator,
which has a regex to search for ftp or http based URLs only.
Is there any chance the URLValidator regexp can
4 matches
Mail list logo