dns & http overview
TRANSCRIPT
Happy Acoustic Instrumental Background Music for Video
Upbeat Acoustic
ClipConvertercc
1141323
eng - Converted with ClipConvertercc
Hello My name is Roman
In todayrsquos presentation I will be going over the different concepts that make up DNS and HTTP
DNS or Domain Name System
bull A globally distributed scalable reliable database made up of large networks of interconnected computers
bull One of the most important parts of the internet bull Most basic form translated webiste names into 10101100sbull Make networks human friendly bull No Internet without DNS
bull Comprised of three componentsbull A ldquoname spacerdquobull Servers making that name space availablebull Resolvers (clients) which query the servers about the name space
Primary Server -holds the master copy of the data for a zone-notifies secondary server of changes ndashnotify request-responds to queries from Secondary Servers
Secondary Server-have copies of the primary DNS data synchronized through zone tranfers-when prompted or at intervals query Primary Servers for DNS record changes (redundancy)-any changes done to Primary Server is copied through zone transfers
com net au info biz
com net
org
org
OtherccTLDs
id
internal prosrs
google yahoo theagemicrosoftausregistry
ldquorootrdquo zone
TLDs amp ccTLDs
2LD
3LD
4LD
DNS ResolutionThe process of website namersquos name into an IP address or vice versa
Root server is asked about the domain name that needs to be resolved If the server doesnrsquot know it will contact another name server until it finds the authoritative server
resposible for the domain Authoritative server responds with a cachable info for browser to process
DNS DelegationProcess of distibuting the namespace into more zones Used traffic distribution DNS
performanance resolution fault tolerance adding new branches locations
DNS server make upClient Server
pcRecursive Servers
DNS info from resolvers queries multiple servers
Root ServerTop level domain
hierarchy contacts others
Authoritative ServersServer in charge of a given zone has domain registration records
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Hello My name is Roman
In todayrsquos presentation I will be going over the different concepts that make up DNS and HTTP
DNS or Domain Name System
bull A globally distributed scalable reliable database made up of large networks of interconnected computers
bull One of the most important parts of the internet bull Most basic form translated webiste names into 10101100sbull Make networks human friendly bull No Internet without DNS
bull Comprised of three componentsbull A ldquoname spacerdquobull Servers making that name space availablebull Resolvers (clients) which query the servers about the name space
Primary Server -holds the master copy of the data for a zone-notifies secondary server of changes ndashnotify request-responds to queries from Secondary Servers
Secondary Server-have copies of the primary DNS data synchronized through zone tranfers-when prompted or at intervals query Primary Servers for DNS record changes (redundancy)-any changes done to Primary Server is copied through zone transfers
com net au info biz
com net
org
org
OtherccTLDs
id
internal prosrs
google yahoo theagemicrosoftausregistry
ldquorootrdquo zone
TLDs amp ccTLDs
2LD
3LD
4LD
DNS ResolutionThe process of website namersquos name into an IP address or vice versa
Root server is asked about the domain name that needs to be resolved If the server doesnrsquot know it will contact another name server until it finds the authoritative server
resposible for the domain Authoritative server responds with a cachable info for browser to process
DNS DelegationProcess of distibuting the namespace into more zones Used traffic distribution DNS
performanance resolution fault tolerance adding new branches locations
DNS server make upClient Server
pcRecursive Servers
DNS info from resolvers queries multiple servers
Root ServerTop level domain
hierarchy contacts others
Authoritative ServersServer in charge of a given zone has domain registration records
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
DNS or Domain Name System
bull A globally distributed scalable reliable database made up of large networks of interconnected computers
bull One of the most important parts of the internet bull Most basic form translated webiste names into 10101100sbull Make networks human friendly bull No Internet without DNS
bull Comprised of three componentsbull A ldquoname spacerdquobull Servers making that name space availablebull Resolvers (clients) which query the servers about the name space
Primary Server -holds the master copy of the data for a zone-notifies secondary server of changes ndashnotify request-responds to queries from Secondary Servers
Secondary Server-have copies of the primary DNS data synchronized through zone tranfers-when prompted or at intervals query Primary Servers for DNS record changes (redundancy)-any changes done to Primary Server is copied through zone transfers
com net au info biz
com net
org
org
OtherccTLDs
id
internal prosrs
google yahoo theagemicrosoftausregistry
ldquorootrdquo zone
TLDs amp ccTLDs
2LD
3LD
4LD
DNS ResolutionThe process of website namersquos name into an IP address or vice versa
Root server is asked about the domain name that needs to be resolved If the server doesnrsquot know it will contact another name server until it finds the authoritative server
resposible for the domain Authoritative server responds with a cachable info for browser to process
DNS DelegationProcess of distibuting the namespace into more zones Used traffic distribution DNS
performanance resolution fault tolerance adding new branches locations
DNS server make upClient Server
pcRecursive Servers
DNS info from resolvers queries multiple servers
Root ServerTop level domain
hierarchy contacts others
Authoritative ServersServer in charge of a given zone has domain registration records
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Primary Server -holds the master copy of the data for a zone-notifies secondary server of changes ndashnotify request-responds to queries from Secondary Servers
Secondary Server-have copies of the primary DNS data synchronized through zone tranfers-when prompted or at intervals query Primary Servers for DNS record changes (redundancy)-any changes done to Primary Server is copied through zone transfers
com net au info biz
com net
org
org
OtherccTLDs
id
internal prosrs
google yahoo theagemicrosoftausregistry
ldquorootrdquo zone
TLDs amp ccTLDs
2LD
3LD
4LD
DNS ResolutionThe process of website namersquos name into an IP address or vice versa
Root server is asked about the domain name that needs to be resolved If the server doesnrsquot know it will contact another name server until it finds the authoritative server
resposible for the domain Authoritative server responds with a cachable info for browser to process
DNS DelegationProcess of distibuting the namespace into more zones Used traffic distribution DNS
performanance resolution fault tolerance adding new branches locations
DNS server make upClient Server
pcRecursive Servers
DNS info from resolvers queries multiple servers
Root ServerTop level domain
hierarchy contacts others
Authoritative ServersServer in charge of a given zone has domain registration records
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
com net au info biz
com net
org
org
OtherccTLDs
id
internal prosrs
google yahoo theagemicrosoftausregistry
ldquorootrdquo zone
TLDs amp ccTLDs
2LD
3LD
4LD
DNS ResolutionThe process of website namersquos name into an IP address or vice versa
Root server is asked about the domain name that needs to be resolved If the server doesnrsquot know it will contact another name server until it finds the authoritative server
resposible for the domain Authoritative server responds with a cachable info for browser to process
DNS DelegationProcess of distibuting the namespace into more zones Used traffic distribution DNS
performanance resolution fault tolerance adding new branches locations
DNS server make upClient Server
pcRecursive Servers
DNS info from resolvers queries multiple servers
Root ServerTop level domain
hierarchy contacts others
Authoritative ServersServer in charge of a given zone has domain registration records
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
DNS ResolutionThe process of website namersquos name into an IP address or vice versa
Root server is asked about the domain name that needs to be resolved If the server doesnrsquot know it will contact another name server until it finds the authoritative server
resposible for the domain Authoritative server responds with a cachable info for browser to process
DNS DelegationProcess of distibuting the namespace into more zones Used traffic distribution DNS
performanance resolution fault tolerance adding new branches locations
DNS server make upClient Server
pcRecursive Servers
DNS info from resolvers queries multiple servers
Root ServerTop level domain
hierarchy contacts others
Authoritative ServersServer in charge of a given zone has domain registration records
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
DNS server make upClient Server
pcRecursive Servers
DNS info from resolvers queries multiple servers
Root ServerTop level domain
hierarchy contacts others
Authoritative ServersServer in charge of a given zone has domain registration records
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
DNS DelegationProcess of distributing the namespace into more zones Used
traffic distribution DNS performanance resolution fault tolerance adding new branches locations
Forward amp Reverse DNS resolutionsName into IP = Forward ResolutionIP into Name = Reverse Resolution
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
DNS record ndash single entry that gives the ZONE instructions
DNS Record consists ofRecord nameRecord valueTime to live (TTL)
DNS Zone A container of all the DNS records for a specific domainExample visitkrakowcom wwwvisitkrakowcom
blogvisitkrakowcom DNS records that make up DNS ZONE mailvisitkrakowcom
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Blank NameRecord that has nothing in the name slotEx Visitkrakowcom vs wwwvisitkrakowcom
No data for record type has www as itrsquos record name
A Recordbull Used to point a domain or a subdomain to an IP addressbull Point one domain to multiple IP addresses (redundancyload balancingperformnce)
C NAME (Canonical Name )bull DNS entry used to point a host name to a host namebull Allows changes to the IP address of a server or cluster of servers without making DNS changesbull Docsexamplecom and documentsexamplecom acess the same files
MX Records (Mail Exchange)bull Used to route email according to ownerrsquos preferencesbull Allows you to specify multiple mail servers to be used
documentsexamplecom to docsexamplecomdocumentsexamplecom to docsexamplecom
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
SPF Records (Sender Policy Framework)bull Open standard created to prevent Address forgerybull Current versions SPFv1SPF Classic protect sender
bull Domain owner publishes SPF info in domainrsquos DNS Zonebull Receiving server can check if the message complies with the domainrsquos stated policy If the message comes
from an inkown sender it will be considered fake and discarded bull The receiving server needs to keep of SPF information
bull NS (name server)bull Name Server (NS) records identify the name servers that are authoritative for
the DNS zone
bull TTL (Time to LIve)bull Total value in seconds how the DNS record will be cached before it needs to be refreshed A queried
Name Server will check TTL to see how ling before it has to refresh and if the DNS record was delivered on time
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Record ValueThe data that tells DNS record where you want it to point
Uniform Resource Locator (URL)A URL is the web address of a resource on the Internet This is the address you type in a browser to visit a particular web site For example wwwvisitkrakowcom
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
HTTP Hypertransfer Text amp Protocol
Communication protocol used to send data from one program to another over the Internet Most significatnt protocol on the internet port80
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
HTTP communication between a client and a server
bull Server listens
bull Server accepts and records request
bull Server can continue to accept other requests
bull Server writes responses of requests
bull Server ends response
bull Business Applications
bull Database Server
Client connects
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Web Application Components
Web Browser presents the user interface
Web Server processes HTTP requests
Business Application processes requests at the application level by providing a service
Database Server maintains the database by processing query and update requests from the application
HTTP is the language that web clients and web servers use to talk to each other
HTTP is largely ldquounder the hoodrdquo but a basic understanding can be helpful
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Web Browser Responsibilities
bull User Interface Presentationbull Client-Server Communication (HTTP)bull Cache Controlbull Cookie Managementbull Handling Embedded Objectsbull Script Interpretation
bull User Interface Presentationbull Parse HTML and CSS codebull handle errorsbull Format and present a graphical displaybull Handle user interactionsbull scroll mouse movement click etc
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
The Client sends a message to the Server at a particular port (80 is the default)The first part of the message is the request line containing
A method (HTTP command) such as GET or POSTA document address andAn HTTP version number
ExampleGET indexhtml HTTP10
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
When a user submits a browser request to a web server it sends two categories of data
Form Data Data that the user explicitly typed into an HTML formFor example registration information
HTTP Request Header Data Data that is automatically appended to the HTTP Request from the client
For example cookies browser type etc
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Other methods beside GET and POST are
HEAD Like GET but ask that only a header be returnedPUT Request to store the entity-body at the URIDELETE Request removal of data at the URILINK Request header information be associated with a document on the serverUNLINK Request to undo a LINK requestOPTIONS Request information about communications options on the serverTRACE Request that the entity-body be returned as received (used for debugging)
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
The second part of a request is optional header information such asWhat the client software isWhat formats it can accept
All information is in the form Name ValueExample
User-Agent Mozilla202Gold (WinNT I)Accept imagegif imagejpeg
A blank line ends the header
Accept typesubtype typesubtype Specifies media types that the client prefers to accept
Accept-Language en fr dePreferred language (For example English French German)
User-Agent stringThe browser or other client program sending the request
From daveacmorgEmail address of user of client program
Cookie name=valueInformation about a cookie for that URLMultiple cookies can be separated by commas
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
In this example the client wants to send data to the server We use the POST method The request line shows the method (POST) URL and HTTP version (11) There are four lines of headers The request body contains the input information The response message contains the status line and four lines of headers The created document which is a CGI document is included as the body
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Response headers
Server NCSA13Name and version of the server
Content-Type typesubtypeShould be of a type and subtype specified by the clientrsquos Accept header
Set-Cookie name=value optionsRequests the client to store a cookie with the given name and value
http-equiv and content typically have the same kinds of values as in the HTTP headerThis tag asks the client to pretend that the information actually occurred in the header
The information is not really in the headerThis tag is available because you have little direct control over what is in the header (unless you write your own server)As usual not all browsers handle this information the same way
Example ltmeta http-equiv=Set-Cookie content=value=nexpires=date path=url
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Summary
HTTP is a fairly straightforward protocol with a lot of possible kinds of predefined header information More kinds can be added so long as client and server agree
A request from the client consists of three parts1 A header line2 A block of header information ending with a blank line3 The (optional) entity body containing data
A response from the server consists of the same three parts HTTP headers are ldquounder the hoodrdquo information not normally displayed to the user
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-
Thanks
Any Questions
romanwlodarski
romanwlodarskigmailcom
- Slide 1
- Hello
- Slide 3
- DNS or Domain Name System
- Primary Server -holds the master copy of the data for a zone
- Slide 6
- Slide 7
- DNS server make up
- Slide 9
- DNS record ndash single entry that gives the ZONE instructions
- Slide 12
- Slide 13
- Slide 14
- HTTP Hypertransfer Text amp Protocol
- Slide 16
- Web Application Components
- Web Browser Responsibilities
- Slide 19
- Other methods beside GET and POST are HEAD Like GET but as
- Slide 22
- Slide 23
- (2)
- Summary
- Thanks
-