ASP – Server Object – Access Core Features of Classic ASP with Server Methods

Introduction – What Is the Server Object in Classic ASP?

In Classic ASP, the Server object is a built-in global object that provides access to essential server-side functions. It allows your ASP scripts to create objects, encode/transfer data, and manage errors—all at the server level.

In this guide, you’ll learn:

• What the Server object is and why it matters
• Key methods like CreateObject, HTMLEncode, URLEncode, and MapPath
• Examples of using these methods in Classic ASP pages
• Output examples and practical use cases

Core Methods of the Server Object

1. Server.CreateObject()

Used to create instances of server-side components like CDOSYS or ADODB.

<%
Dim conn
Set conn = Server.CreateObject("ADODB.Connection")
%>

Use Case: Working with databases, emails, file system, etc.

2. Server.HTMLEncode()

Prevents HTML injection by converting special characters into entities.

<%
Dim unsafeText
unsafeText = "<script>alert('XSS')</script>"
Response.Write Server.HTMLEncode(unsafeText)
%>

Output:
<script>alert('XSS')</script>

3. Server.URLEncode()

Encodes URLs before passing them into query strings.

<%
Dim user
user = "John Smith"
Response.Write "Welcome.aspx?name=" & Server.URLEncode(user)
%>

Output:
Welcome.aspx?name=John%20Smith

4. Server.MapPath()

Translates a virtual path into an actual server path.

<%
Dim path
path = Server.MapPath("data/file.txt")
Response.Write path
%>

Output (example):
C:\inetpub\wwwroot\yourapp\data\file.txt

5. Server.GetLastError() (ASP 3.0+)

Returns the last runtime error object.

<%
On Error Resume Next
Dim x
x = 1 / 0 ' Error

Dim errObj
Set errObj = Server.GetLastError()

If Not errObj Is Nothing Then
    Response.Write "Error: " & errObj.Description
End If
%>

Output:
Error: Division by zero

6. Server.Execute() & Server.Transfer()

• Execute() runs another .asp file’s contents within the current file
• Transfer() redirects execution to another .asp file without returning

<%
Server.Execute("footer.asp")
%>

<%
Server.Transfer("dashboard.asp")
%>

Example – Securely Output User Data

<%
Dim comment
comment = "<b>Great Post!</b>"
Response.Write "User comment: " & Server.HTMLEncode(comment)
%>

Output:
User comment: <b>Great Post!</b>

Best Practices for Using Server Object

Do:

• Use MapPath to work with server files securely
• Encode URLs and HTML using URLEncode and HTMLEncode
• Use CreateObject for database/email integration

Avoid:

• Trusting raw user input—always encode or sanitize
• Using Transfer if the page must return to original
• Overusing CreateObject without Set = Nothing cleanup

Summary – Recap & Next Steps

The Server object in Classic ASP is your gateway to powerful backend operations. From handling errors to executing components and safely rendering content, Server provides essential utilities for robust application development.

Key Takeaways:

• CreateObject is used for COM components like ADODB, CDOSYS
• HTMLEncode/URLEncode help prevent XSS or encoding issues
• MapPath resolves server-side file paths

Real-world Use Cases:

• Sending emails with CDOSYS
• Logging activity to server-side files
• Encoding data safely in search filters or URLs

FAQs – Classic ASP Server Object

What is the difference between Execute() and Transfer()?
Execute() runs the other ASP page and returns to the caller; Transfer() ends the current page and sends control permanently.

Can I use MapPath to write files?
Yes. Use Server.MapPath() to resolve the real path before opening or writing files using FileSystemObject.

Why should I use HTMLEncode()?
It prevents cross-site scripting (XSS) by rendering user-generated content as safe HTML text.