Looks like this is similar and shows that people want other protocols as well: http://stackoverflow.com/questions/8778416/what-are-the-valid-values-for-a-django-url-field
You could modify the validator's regex but I imagine the cleanest way to do this would be to make a copy of it in your own 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 <[email protected]>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 has a regex to search for ftp or http based URLs only. > > Is there any chance the URLValidator regexp can be updated to include ws > as a valid protocol qualifier too? > > Also, more generally, what is the recommended procedure for proposing > changes (and accompanying code) such as this? > > -- > You received this message because you are subscribed to the Google Groups > "Django users" group. > To view this discussion on the web visit > https://groups.google.com/d/msg/django-users/-/ap-_kaacEngJ. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/django-users?hl=en. > -- You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/django-users?hl=en.
