If you are looking for a quick and easy way to encrypt the URLs, why not
create some Middleware which encrypts/decrypts them on the fly with a
secret string from settings?
Although, the URLs are going to look ugly as sin, and I wouldn't
recommend this if you want decent SEO lol.
Remember you'd have to cater for encrypting redirects, query string
separation etc, and you've have to overwrite the request META vars so
that the app logic doesn't need to be patched.
Cal
On 09/05/2011 19:43, ALJ wrote:
I was really looking for something lightweight. I didn't really want
to have to change the model structure to include a UUID ... although I
realise that this seems to way to go. I really just wanted to avoid
any 'opportunistic' attempts at extracting the data. The data itself
isn't critical and not worth the effort of going to great lengths to
crack any encryption I would put in. I was tempted to just use base64,
perhaps joining the PK and the postcode for example. That might be
enough just to obfuscate the id a bit and have a pseudo dual key.
Oh well.
Thanks anyway.
ALJ
--
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.
