Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
Is it safe for me to evaluate a query string’s string and take case (upper/lower) into consideration? Do some browsers lower the whole string for example? Is it reliable enough to code as though whatever parameters I add onto the query strings to remain the same case-wise? (Obviously putting to one side the fact that users might mess with it).
Tagged with C# as I’m not sure if the platform evaluating the query string affects the answer to this question; and it’s C# I’m coding in.
Convention is key. If you use camel-cased query strings throughout your app, use camel-case, etc. You’re going to be the one passing arguments and specifying query strings, so keep it consistent to make life easy on yourself. Other than keeping it consistent, there’s no real benefit to a particular casing convention.
The browser will keep capitalization in tact.