Wrox Programmer Forums

Need to download code?

View our list of code downloads.

Go Back   Wrox Programmer Forums > ASP.NET and ASP > ASP.NET 2.0 > ASP.NET 2.0 Professional
Password Reminder
Register | FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read
ASP.NET 2.0 Professional If you are an experienced ASP.NET programmer, this is the forum for your 2.0 questions. Please also see the Visual Web Developer 2005 forum.
Welcome to the p2p.wrox.com Forums.

You are currently viewing the ASP.NET 2.0 Professional section of the Wrox Programmer to Programmer discussions. This is a community of tens of thousands of software programmers and website developers including Wrox book authors and readers. As a guest, you can read any forum posting. By joining today you can post your own programming questions, respond to other developers’ questions, and eliminate the ads that are displayed to guests. Registration is fast, simple and absolutely free .
DRM-free e-books 300x50
Thread Tools Search this Thread Display Modes
  #1 (permalink)  
Old May 11th, 2006, 02:45 PM
jminatel's Avatar
Wrox Staff
Points: 18,895, Level: 59
Points: 18,895, Level: 59 Points: 18,895, Level: 59 Points: 18,895, Level: 59
Activity: 100%
Activity: 100% Activity: 100% Activity: 100%
Join Date: May 2003
Location: Indianapolis, IN, USA.
Posts: 1,944
Thanks: 72
Thanked 139 Times in 101 Posts
Default article posted: ASP.NET 2.0 security

We've posted a new article that should be of interest to readers in this ASP.NET 2.0 professional forum. The article is an excerpt from Stefan Schackow's book Professional ASP.NET 2.0 Security, Membership, and Role Management. Here's the beginning:

Using the WebPermission Setting in ASP.NET Partial Trust
One of the permissions defined in ASP.NET's Medium and High partial trust files is System.Net.WebPermission. This is probably one of the most confusing permissions for developers to use due to the interaction between ASP.NET's <trust /> element and the settings for this permission. The default declaration for System.Net.WebPermission looks like this:

                    <URI uri="$OriginHost$"/>
Although a WebPermission can be used to define both outbound and inbound connection permissions, normally, you use WebPermission to define one or more network endpoints that your code can connect to. The default declaration shown previously defines a single connection permission that allows partially trusted code the right to make a connection to the network address defined by the <URI /> element.

And you can read the complete article here.

Jim Minatel
Senior Acquisitions Editor
Wiley Technology Publishing
WROX Press
Blog: http://wroxblog.typepad.com/
Jim's Book of the week: No book this week - Donate to the Red Cross!
Jim Minatel
Associate Publisher, WROX - A Wiley Brand
Did someone here help you? Click on their post!

Thread Tools Search this Thread
Search this Thread:

Advanced Search
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off
Trackbacks are Off
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
Article posted: Using SOAP Headers with ASP.NET jminatel XML 0 May 5th, 2006 04:30 PM
New article posted:Using SOAP Headers with ASP.NET jminatel ASP.NET 2.0 Professional 0 May 5th, 2006 04:28 PM
New .NET Framework 2.0 Article posted jminatel .NET Framework 2.0 0 March 13th, 2006 08:09 PM
New Ajax article posted jminatel Ajax 0 March 13th, 2006 07:40 PM

All times are GMT -4. The time now is 09:33 PM.

Powered by vBulletin®
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.
© 2013 John Wiley & Sons, Inc.