NCS Logo - Click for home page Northstar Developer Center
Platforms
All Platforms
.NET Framework (1.x - 4.x)
Active Server Pages
ASP.NET
C#
SQL Server
VB.NET
Visual Basic

Keywords
.NET Data Types
.NET E-mail
.NET Events
.NET Functions
.NET Object Programming
.NET System.Configuration
.NET System.Diagnostics
.NET System.IO
.NET System.Net
.NET System.Net.Sockets
Active Data Objects
ASP Architecture
ASP Black Belt
ASP Built-in Functions
ASP Built-in Objects
ASP Debugging
ASP Performance
ASP Security
ASP Syntax
ASP.NET Authentication
ASP.NET Controls
ASP.NET Data Access
ASP.NET Features
ASP.NET Master Pages
ASP.NET Page Events
ASP.NET Security
ASP.NET ViewState
Atom
Certifications
COM, DCOM, COM+
Data Access
E-Mail
Errors
Exporting Data
HTML Tips
IIS
Object-Oriented Programming
RSS
SQL
Uncategorized ASP Tips
VB API Programming
VB Forms
VB Syntax
XML

Book Support
Visual Basic 6 Bible
ASP Bible
ASP Weekend Crash Course
ASP.NET At Work
Creating Web Services

Detecting Secured Connection

Written by Eric Smith, Northstar Computer Systems LLC

In a site I built recently, I only wanted the user to hit a particular page by way of a secured HTTPS connection. As I loaded the page, I used the SERVER_PORT variable to see if I was on the secured server, which has a port number of 443. If I was on port 80, I was on the non-secure server. A quick Response.Redirect sent the user to the correct web site. There are also a number of additional variables that provide information about the security on the server, such as the number of bits in the security key, the issuer, and so on. To see an example of the values, take a look at this URL:

<a href=”https://ssl.northcomp.com/variables.asp”>https://ssl.northcomp.com/variables.asp</a>

This page dumps out all the server variables on my secured server. Take note of the CERT_KEYSIZE, CERT_SECRETKEYSIZE, and other variables.

Keywords: [ Uncategorized ASP Tips ]

Publication Date: 2/10/2001