Overview#
HTTP is an Abbreviation of Hypertext Transfer Protocol.HTTP Related to HTTPS
HTTP protocol is stateless#
So even though the HTTP protocol may be stateless the long-term communications between a HTTP client and HTTP server are NOT. There is a considerable number of methods to try to maintain state within long-term communications between a HTTP client and HTTP serverHTTP Status Code#
The HTTP protocol provides a rich set of HTTP Status Code to represent different request processing outcomes.HTTP Methods#
HTTP Methods are request message is characterized by two very important parts. The target, composed by a URI, identifies the resource where an operation should be performed. The request method defines this operation and is the primary source of request semantics.A defining characteristic of HTTP is that the set of available methods is always the same, independent of the target resource. This is in sharp contrast with other architectural styles, such as RPC (Remote Procedure Calls) or distributed objects, where each request target has its own specific operations.
The fixed set of available HTTP Methods.
More Information#
There might be more information for this subject on one of the following:- Accept header
- Accept-Language
- Access Token Type
- Apache Fortress
- Application_type
- Assertion Framework for OAuth 2.0 Client Authentication and Authorization Grants
- Authorization Header
- Authorization Request
- Authorization_endpoint
- BREACH (security exploit)
- Basic Authentication Scheme
- Blockchain 2.0
- CSRF Token
- Cache-Control
- Certificate Management Protocol
- Certificate Validation Tools
- Client_secret_basic
- Content negotiation
- Content-Language
- Cookie
- Create Read Update Delete
- Cross-platform Authentication
- Cross-site request forgery
- Cross-site scripting
- Data In Transit
- Domain Authorization Document
- Extensible Resource Identifier
- Federated Authorization for UMA 2.0
- GCP Cloud CDN
- Google Cloud Security
- HTTP
- HTTP Authentication Framework
- HTTP Body
- HTTP CONNECT
- HTTP Cache Directive
- HTTP Over TLS
- HTTP Referer
- HTTP Response
- HTTP Status Code
- HTTP Strict Transport Security
- HTTP2
- HTTPS
- HTTPServerObject
- How SSL-TLS Works
- How To Crack SSL-TLS
- HttpSessionTimeout
- Hyperlinks
- Hypertext Transfer Protocol
- Hypertext Transfer Protocol Version 2
- Internet Threat Model
- JSESSIONID
- JavaScript Object Notation (JSON) Patch
- Language-Tag
- Linked Data
- Loopback Interface Redirection
- Media-type
- Microservice
- Mod_auth_openidc
- NGINX
- NIST.SP.800-63B
- Ndsconfig Parameters
- Ndstrace
- Novell Access Manager
- NxsettingsDriver
- OAuth
- OAuth 2.0
- OAuth 2.0 Bearer Token Usage
- OAuth 2.0 Security Considerations
- OAuth 2.0 Token Exchange
- OAuth 2.0 for Native Apps
- OAuth Dynamic Client Registration Metadata
- Object storage
- Online Certificate Status Protocol
- OpenID Connect Front-Channel Logout
- OpenID Connect Profile for SCIM Services
- Private-Use URI Scheme Redirection
- Proxy
- Proxy-Based WAM
- RFC 1945
- RFC 2616
- RFC 2617
- RFC 2817
- RFC 4918
- RFC 7230
- RFC 7234
- RFC 7235
- Recommendations for Secure Use of Transport Layer Security (TLS) and Datagram Transport Layer Security (DTLS)
- Reference
- Representational State Transfer
- Resource Action
- SCIM Bulk Request
- SCIM Client
- SCIM Delete Request
- SCIM Schemas Attribute
- Same Origin Policy
- Secure WEB Page Information
- Security Event Token
- Security Token
- Security Token Service
- Session
- Session ID
- Session Initiation Protocol
- Session Management
- SessionData
- Socket Secure
- Token Binding over HTTP
- Transport Layer Security
- URI Fragment Identifiers
- Uniform Resource Identifier
- Universal Links
- Web Authentication
- Web Blog_blogentry_081116_1
- Web Blog_blogentry_101017_1
- Web Blog_blogentry_250816_1
- Web Linking
- Web Service
- Web Storage
- Web host-meta data
- WebFinger
- WebID
- Well-known
- Why OpenID Connect
- World Wide Web
- [#1] - Hypertext_Transfer_Protocol
- based on information obtained 2012-08-10
