HTTP

Introduction

in

    Second Life includes many events that a script can register to process. These events are listed here.

5xx Server Error

in

    The server failed to fulfill an apparently valid request.

  • 500: Internal Server Error
  • 501: Not Implemented
  • 502: Bad Gateway
  • 503: Service Unavailable
  • 504: Gateway Timeout
  • 505: HTTP Version Not Supported
  • 509: Bandwidth Limit Exceeded
  • This status code, while used by many servers, is not an official HTTP status code.

3xx Redirection

    The client must take additional action to complete the request.

Introduction

in

    There are many different HTTP responses. This appendix lists them. This data was taken from WikiPedia (http://www.wikipedia.org
).

Appendix E: HTTP Response Codes

in

Common HTTP response codes.

Summary

    This chapter showed you how to use HTTP security mechanisms. HTTP has two built-in security mechanisms. Firstly, HTTP supports encryption through HTTPS. Secondly, HTTP provides authentication, which requires users to identify themselves.

Recipes

    This chapter includes two recipes. These two recipes will demonstrate the following:

  • Determining if a URL uses HTTPS, and
  • Using HTTP authentication

    The first recipe will introduce you to some of the things that can be done with the HttpWebRequest class. The second recipe shows how to access a site that uses HTTP authentication.

Understanding HTTP Authentication

    As you saw earlier in this chapter, HTTPS allows you to determine that the web server you are connecting to is what it claims to be. HTTP authentication provides the other side of this verification. HTTP authentication allows the server to determine that the web user is who they say that they are.

Using HTTPS in C#

    HTTPS is implemented as a protocol just like HTTP. Whereas an HTTP URL starts with “http”, an HTTPS protocol starts with “https”. For example, the following URL specifies a secure page on the HTTP recipe site:

https://www.httprecipes.com/1/5/https.php

    It is important to understand that a URL starting with “https” is not just a secure version of the same URL beginning with an “http”. Consider the following URL:

Introduction

  • HTTP Security
  • Using HTTPS
  • Using HTTP Authentication
Syndicate content

Copyright 2005 - 2010 by Heaton Research, Inc.. Heaton Research™ and Encog™ are trademarks of Heaton Research. Click here for copyright and trademark information.