Then the validation that the QueryString parameter CngID is an Integer should be in the target page (IndexCNG.aspx), not in the source page. If an invalid querystring is provided, you would simply show that as an error message to the user. (or redirect to an error page).
On Jan 1, 11:03 pm, "m...@ni" <[email protected]> wrote: > ok cerebrus and chuck 1 more thing came to my mind regarding checking > of the querystring,whether it is null or not, the point is that as i > am taking CngId, which means that its gona take only the > integers,because on the basis of this cngId, i have to execute another > functionality,now wat if a user enters 'a' or '#' in the url (as the > querystring is visible in the url) because watever comes in the > querystring, i am assigning it to cngId,ok i got tht how to chk > whehter it is null or not,but how i overcome this problem. > > suppose instead of writing this url > "http://indexCNG.aspx?CngId=1"; > > a person enters this url,then an error came because of that,what to do > in this regard > "http://indexCNG.aspx?CngId=a";
