Net431:advanced net services

Slides:



Advertisements
Similar presentations
TCP/IP Protocol Suite 1 Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display. Chapter 22 World Wide Web and HTTP.
Advertisements

HTTP HyperText Transfer Protocol. HTTP Uses TCP as its underlying transport protocol Uses port 80 Stateless protocol (i.e. HTTP Server maintains no information.
HTTP – HyperText Transfer Protocol
HTTP Hypertext Transfer Protocol. HTTP messages HTTP is the language that web clients and web servers use to talk to each other –HTTP is largely “under.
How the web works: HTTP and CGI explained
TCP/IP Protocol Suite 1 Chapter 22 Upon completion you will be able to: World Wide Web: HTTP Know how HTTP accesses data on the WWW Objectives.
2/9/2004 Web and HTTP February 9, /9/2004 Assignments Due – Reading and Warmup Work on Message of the Day.
 What is it ? What is it ?  URI,URN,URL URI,URN,URL  HTTP – methods HTTP – methods  HTTP Request Packets HTTP Request Packets  HTTP Request Headers.
FTP (File Transfer Protocol) & Telnet
HyperText Transfer Protocol (HTTP).  HTTP is the protocol that supports communication between web browsers and web servers.  A “Web Server” is a HTTP.
CP476 Internet Computing Lecture 5 : HTTP, WWW and URL 1 Lecture 5. WWW, HTTP and URL Objective: to review the concepts of WWW to understand how HTTP works.
TCP/IP Protocol Suite 1 Chapter 22 Upon completion you will be able to: World Wide Web: HTTP Understand the components of a browser and a server Understand.
Rensselaer Polytechnic Institute Shivkumar Kalvanaraman, Biplab Sikdar 1 The Web: the http protocol http: hypertext transfer protocol Web’s application.
Maryam Elahi University of Calgary – CPSC 441.  HTTP stands for Hypertext Transfer Protocol.  Used to deliver virtually all files and other data (collectively.
Tools for Web Applications. Overview of TCP/IP Link Layer Network Layer Transport Layer Application Layer.
HTTP1 Hypertext Transfer Protocol (HTTP) After this lecture, you should be able to:  Know how Web Browsers and Web Servers communicate via HTTP Protocol.
Web Server Design Assignment #1: Basic Operations Due: 02/03/2010 Old Dominion University Department of Computer Science CS 495/595 Spring 2010 Martin.
CIS679: Lecture 13 r Review of Last Lecture r More on HTTP.
Web Server Design Assignment #2: Conditionals & Persistence Due: 02/24/2010 Old Dominion University Department of Computer Science CS 495/595 Spring 2010.
Operating Systems Lesson 12. HTTP vs HTML HTML: hypertext markup language ◦ Definitions of tags that are added to Web documents to control their appearance.
WEB SERVER Mark Kimmet Shana Blair. The Project Web Server Application  Receives request for web pages or images from a client browser via the internet.
2: Application Layer 1 Chapter 2: Application layer r 2.1 Principles of network applications  app architectures  app requirements r 2.2 Web and HTTP.
CITA 310 Section 2 HTTP (Selected Topics from Textbook Chapter 6)
27.1 Chapter 27 WWW and HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
27.1 Chapter 27 WWW and HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
EE 122: Lecture 21 (HyperText Transfer Protocol - HTTP) Ion Stoica Nov 20, 2001 (*)
27.1 Chapter 27 WWW and HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
1 Chapter 22 World Wide Web (HTTP) Chapter 22 World Wide Web (HTTP) Mi-Jung Choi Dept. of Computer Science and Engineering
Lecture # 1 By: Aftab Alam Department Of Computer Science University Of Peshawar Internet Programming.
Hypertext Transfer Protocol
Block 5: An application layer protocol: HTTP
How HTTP Works Made by Manish Kushwaha.
Content from Python Docs.
HTTP – An overview.
Hypertext Transfer Protocol
The Hypertext Transfer Protocol
HTTP request message: general format
How does it work ?.
COMP2322 Lab 2 HTTP Steven Lee Feb. 8, 2017.
Chapter 27 WWW and HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
HTTP Protocol Specification
Hypertext Transport Protocol
Web Caching? Web Caching:.
IE.
Web Server Design Assignment #2: Conditionals & Persistence
HTTP Protocol.
Tutorial (4): HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
IS333D: MULTI-TIER APPLICATION DEVELOPMENT
Hypertext Transfer Protocol
HTTP Request Method URL Protocol Version GET /index.html HTTP/1.1
Hypertext Transfer Protocol
Hypertext Transfer Protocol
Web Server Design Assignment #2: Conditionals & Persistence
HyperText Transfer Protocol
EE 122: HyperText Transfer Protocol (HTTP)
Hypertext Transfer Protocol (HTTP)
Web Server Design Week 6 Old Dominion University
World Wide Web Uniform Resource Locator hostname [:port]/path
Hypertext Transfer Protocol
Chapter 27 WWW and HTTP Copyright © The McGraw-Hill Companies, Inc. Permission required for reproduction or display.
Kevin Harville Source: Webmaster in a Nutshell, O'Rielly Books

Traditional Internet Applications
HTTP Hypertext Transfer Protocol
Hypertext Transfer Protocol
Web Server Design Week 6 Old Dominion University
CSCI-351 Data communication and Networks
Web Server Design Week 7 Old Dominion University
Web Server Design Week 7 Old Dominion University
Presentation transcript:

Net431:advanced net services Networks and Communication Department Tutorial 4

at least any two general headers, any two request headers, Q1: Show a request that retrieves the document /usr/users/doc/doc1. Use : at least any two general headers, any two request headers, And any one entity header. 27-Nov-18 Networks and Communication Department

GET /usr/users/doc/doc.1 HTTP /1.1 Date: Fri, 13-Jan-06 08:45:20 GMT MIME-version: 1.0 Accept: image/gif Accept: image/jpeg Last modified: Mon, 09-Jan-06 27-Nov-18 Networks and Communication Department

Q2. Show the response to Question #1, 1 for a successful request with four lines of header. The header lines define the date, server, MIME version, and length of the document for a document with 4623 lines. 27-Nov-18 Networks and Communication Department

HTTP/1.1 200 OK Date: Fri, 13-Jan-06 08:45:25 GMT Server: Challenger MIME-version: 1.0 Content-length: 4623 (Body of document) 27-Nov-18 Networks and Communication Department

Q3: Show the response to Question #1 for a document that has permanently moved to /usr/deads/doc1. With three lines of header defines the date, new server name and new location. 27-Nov-18 Networks and Communication Department

HTTP/1.1 301 Moved permanently Date: Fri, 13-Jan-06 08:45:25 GMT Server: Challenger Location: /usr/deads/doc.1 27-Nov-18 Networks and Communication Department

Q4: Show the response to Question #1 if there is a syntax error in the request. With two headers for server and date. 27-Nov-18 Networks and Communication Department

HTTP/1.1 400 Bad Request Date: Fri, 13-Jan-06 08:45:25 GMT Server: Challenger 27-Nov-18 Networks and Communication Department

Q5. Show the response to Question#1 if the client is unauthorized to access the document with two headers for server and the date of access. 27-Nov-18 Networks and Communication Department

HTTP/1.1 401 Unauthorized Date: Fri, 13-Jan-06 08:45:25 GMT Server: Challenger 27-Nov-18 Networks and Communication Department

Q6: Show a request that asks for information about a document at /bin/users/file. Use at least: two general headers. and one request header. 27-Nov-18 Networks and Communication Department

HEAD /bin/users/file HTTP /1.1 Date: Fri, 13-Jan-06 10:40:22 GMT MIME-version: 1.0 From: mzzchen@sinonet.cn 27-Nov-18 Networks and Communication Department

Q7: Show a request to retrieve the file at location /bin/etc/file Q7: Show a request to retrieve the file at location /bin/etc/file!. The client needs the document of any type of medium only if it was modified after January 23, 1999. use four line of headers. With date and MIME-version. 27-Nov-18 Networks and Communication Department

GET /bin/etc/file1 HTTP /1 GET /bin/etc/file1 HTTP /1.1 Date: Fri, 13-Jan-06 11:22:08 GMT MIME-version: 1.0 Accept: */* If-modified-since: 23-Jan-1999 00:00:00 GMT 27-Nov-18 Networks and Communication Department

Q8: Show a request to send and store a file at location /bin/letter Q8: Show a request to send and store a file at location /bin/letter. The client Should identifies the types of documents it can accept (text/html), (gif), (jpeg). There will be six lines of header with (date, MIME-version). 27-Nov-18 Networks and Communication Department

PUT /bin/letter HTTP /1.1 Date: Fri, 13-Jan-06 11:47:00 GMT MIME-version: 1.0 Accept: text/html Accept: image/gif Accept: image/jpeg Location: /bin/letter 27-Nov-18 Networks and Communication Department

Q9: Show the response to Question#8 Q9: Show the response to Question#8. The response shows seven lines of headers the age of the document, Server, MIME- version, content type and length as well as the date and time when the contents may change. 27-Nov-18 Networks and Communication Department

Content-type: text/html Content-length: 6324 Age: 10:06:02 HTTP/1.1 200 OK Date: Fri, 13-Jan-06 11:51:02 GMT Server: Challenger MIME-version: 1.0 Content-type: text/html Content-length: 6324 Age: 10:06:02 Expires: 09-May-06 00:00:00 GMT 27-Nov-18 Networks and Communication Department

Q10: Compare between Persistent vs non- persistent HTTP connections? 27-Nov-18 Networks and Communication Department

Persistent vs non-persistent HTTP connections default for HTTP/1.1 on same TCP connection: server, parses request, responds, parses new request,.. less slow start. HTTP/1.0 server parses request, responds, and closes TCP connection Each object transfer suffers from slow start

Q&A 27-Nov-18 Networks and Communication Department