but someone who really wanted those string values could easily decode them. You could probably base64 encode some string values, and that would be easier. That would probably be one of the most secure options, but also a lot of work which may be unnecessary. First, you could do some kind of encryption, which is decrypted at page load. If you really had a value that you never wanted a user to see, you would have a couple of options. Most of the time, it's your user who is viewing the source, and the string values on the client are intended for their use, so that sort of private string value isn't often necessary. Of course, by packaging up your source into a garbled, minified mess, you have a light version of security through obscurity. Keeping string values private is a different concern, and obfuscation won't really be of much benefit. UPDATE: This question was originally asked on 2008, and The mentioned technologies are deprecated. It's a very popular tool, built, enhanced and maintained by the Yahoo UI team.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |