Talk:ASP.NET: Difference between revisions

Content deleted Content added
mNo edit summary
Line 15:
It seems there is no (easy) way to share session state between ASP.NET and legacy (or classic) ASP pages both placed in the same directory (hence in a same web application). There a lot of solutions involving databases and a lot of changes on both places (ASP.NET and ASP), but nothing working out-of-the-box. Is it possible this statement to be valid only for ASP.NET applications, say one that is 1.1 and another that is 2.0?
--[[Special:Contributions/85.130.3.78|85.130.3.78]] ([[User talk:85.130.3.78|talk]]) 11:23, 23 March 2009 (UTC)
 
== Is it secure, and how would I know if it is? ==
 
I recently ran across a site where the extension was .aspx with a form where a credit card number, and expiration was all being displayed in plain text. Granted that a person using some sort of sniffing software could get all the info anyway, not recognizing the extension I immediately backed out, discontinuing the transaction before entering all the required data.
 
Is it secure, and how would I, or any normal user know if it is indeed secure or not? <small><span class="autosigned">—Preceding [[Wikipedia:Signatures|unsigned]] comment added by [[User:Kittyrinn|Kittyrinn]] ([[User talk:Kittyrinn|talk]] • [[Special:Contributions/Kittyrinn|contribs]]) 04:44, 15 May 2009 (UTC)</span></small><!-- Template:Unsigned --> <!--Autosigned by SineBot-->
 
:There is no way to be sure a page is secure. There is a way to be sure your data is send in a secure manner by using [[Https]], this will however not say anything about waht the page itself does with the data. The ASPX itself is as secure as the programmer is able to make it, as is the same with .php and other serverside script pages. -- [[Special:Contributions/94.210.224.69|94.210.224.69]] ([[User talk:94.210.224.69|talk]]) 15:01, 9 June 2009 (UTC)
 
==Clean code==