CS615 - Aspects of System Administration



Similar documents
Internet Technologies Internet Protocols and Services

Domain Name System (DNS)

Linux Administrator (Advance)

reference: HTTP: The Definitive Guide by David Gourley and Brian Totty (O Reilly, 2002)

Mail system components. Electronic Mail MRA MUA MSA MAA. David Byers

CSI Lab 1 : Exercise Find the IP address of Or, another way:

The Application Layer. CS158a Chris Pollett May 9, 2007.

Network Technologies

GET /FB/index.html HTTP/1.1 Host: lmi32.cnam.fr

Mail agents. Introduction to Internet Mail. Message format (2) Authenticating senders

The Hyper-Text Transfer Protocol (HTTP)

Protocolo HTTP. Web and HTTP. HTTP overview. HTTP overview

Application layer Web 2.0

People Data and the Web Forms and CGI CGI. Facilitating interactive web applications

Chapter 27 Hypertext Transfer Protocol

URLs and HTTP. ICW Lecture 10 Tom Chothia

HTTP. Internet Engineering. Fall Bahador Bakhshi CE & IT Department, Amirkabir University of Technology

CipherMail Gateway Quick Setup Guide

Simple Mail Transfer Protocol

HTTP Protocol. Bartosz Walter

Hypertext for Hyper Techs

Web. Services. Web Technologies. Today. Web. Technologies. Internet WWW. Protocols TCP/IP HTTP. Apache. Next Time. Lecture # Apache.

Outline Definition of Webserver HTTP Static is no fun Software SSL. Webserver. in a nutshell. Sebastian Hollizeck. June, the 4 th 2013

CS640: Introduction to Computer Networks. Applications FTP: The File Transfer Protocol

1 Introduction: Network Applications

SMTP Servers. Determine if an message should be sent to another machine and automatically send it to that machine using SMTP.

Workflow Configuration on R12/R11. High Level Steps. SENDMAIL configuration mostly done by System Administrator Workflow configuration for R12

Modern Web Development From Angle Brackets to Web Sockets

security

Glossary of Technical Terms Related to IPv6

Internet Technologies. World Wide Web (WWW) Proxy Server Network Address Translator (NAT)

CS 164 Winter 2009 Term Project Writing an SMTP server and an SMTP client (Receiver-SMTP and Sender-SMTP) Due & Demo Date (Friday, March 13th)

Evolution of the WWW. Communication in the WWW. WWW, HTML, URL and HTTP. HTTP Abstract Message Format. The Client/Server model is used:

CONTENT of this CHAPTER

World Wide Web. Before WWW

1. When will an IP process drop a datagram? 2. When will an IP process fragment a datagram? 3. When will a TCP process drop a segment?

Articles Fighting SPAM in Lotus Domino

CTIS 256 Web Technologies II. Week # 1 Serkan GENÇ

Setup Local Mail Server Using Postfix, Dovecot And Squirrelmail On CentOS 6.5/6.4

Cache All The Things

CS43: Computer Networks . Kevin Webb Swarthmore College September 24, 2015

The Web History (I) The Web History (II)

The basic groups of components are described below. Fig X- 1 shows the relationship between components on a network.

QMAIL & SMTP: A Secure Application for an Unsecure Protocol. Orr Dunkelman. orrd@vipe.technion.ac.il. January 27, 2004 SMTP and QMAIL Slide 1

policyd-weight and some unorthodox approaches to eliminating spam

Management CSCU9B2 CSCU9B2 1

Cannot send Autosupport , error message: Unknown User

Evolution of the WWW. Communication in the WWW. WWW, HTML, URL and HTTP. HTTP - Message Format. The Client/Server model is used:

Table of Contents. Open-Xchange Authentication & Session Handling. 1.Introduction...3

Internet Security [1] VU Engin Kirda

Cyber Security Workshop Ethical Web Hacking

Lecture 2. Internet: who talks with whom?

APACHE WEB SERVER. Andri Mirzal, PhD N

Postfix. by Rod Roark

The Application Layer: DNS

For internal circulation of BSNL only

Table of Contents. Electronic mail. History of (2) History of (1) history. Basic concepts. Aka (or according to Knuth)

Module 45 (More Web Hacking)

. MIME is the protocol that was devised to allow non-ascii encoded content in an and attached files to an .

APACHE HTTP SERVER 2.2.8

Computer Networks. Lecture 7: Application layer: FTP and HTTP. Marcin Bieńkowski. Institute of Computer Science University of Wrocław

MailFoundry Users Manual. MailFoundry User Manual Revision: MF Copyright 2005, Solinus Inc. All Rights Reserved

The Web: some jargon. User agent for Web is called a browser: Web page: Most Web pages consist of: Server for Web is called Web server:

CIT 380: Securing Computer Systems

Web applications. Web security: web basics. HTTP requests. URLs. GET request. Myrto Arapinis School of Informatics University of Edinburgh

Internet Technology 2/13/2013

Data Communication I

CloudOYE CDN USER MANUAL

Project #2. CSE 123b Communications Software. HTTP Messages. HTTP Basics. HTTP Request. HTTP Request. Spring Four parts

Applications and Services. DNS (Domain Name System)

A Beginner's Guide to Setting Up A Web Hosting System (Or, the design and implementation of a system for the worldwide distribution of pictures of

Services Deployment. Administrator Guide

Chakchai So-In, Ph.D.

TCP/IP Networking An Example

Introduction to Computer Security Benoit Donnet Academic Year

Introduction to Computer Networks

HTTP Fingerprinting and Advanced Assessment Techniques

Architecture of So-ware Systems HTTP Protocol. Mar8n Rehák

By Bardia, Patit, and Rozheh

Implementing MDaemon as an Security Gateway to Exchange Server

GL-275: Red Hat Linux Network Services. Course Outline. Course Length: 5 days

Math SMTP Server Configuration

Instructor: Betty O Neil

IxLoad TM : Data HTTP, SSL, and FTP

Certified Spam Assassin Professional VS-1114

Basic Internet programming Formalities. Hands-on tools for internet programming

CSE331: Introduction to Networks and Security. Lecture 12 Fall 2006

3.1 SESSION INITIATION PROTOCOL (SIP) OVERVIEW

W3Perl A free logfile analyzer

"Charting the Course... Enterprise Linux Networking Services Course Summary

Government of Canada Managed Security Service (GCMSS) Annex A-5: Statement of Work - Antispam

ENTERPRISE LINUX NETWORKING SERVICES

. Daniel Zappala. CS 460 Computer Networking Brigham Young University

Load Balancing/High Availability Configuration for neoninsight Server

Transcription:

CS615 - Aspects of System Administration Slide 1 CS615 - Aspects of System Administration SMTP, HTTP Department of Computer Science Stevens Institute of Technology Jan Schaumann jschauma@stevens-tech.edu http://www.cs.stevens-tech.edu/~jschauma/615/

Send me an email! CS615 - Aspects of System Administration Slide 2 Start an EC2 instance and send a mail from it to jschauma@stevens.edu with a subject line of CS615 - SMTP Exercise.

/var/log/maillog CS615 - Aspects of System Administration Slide 3 Sending... Apr 11 21:23:47 localhost postfix/pickup[7534]: A57862E4B: uid=1000 from=<fedora> Apr 11 21:23:47 localhost postfix/cleanup[7561]: A57862E4B: message-id=<20150411 212347.A57862E4B@ip-10-65-168-165.localdomain> Apr 11 21:23:47 localhost postfix/qmgr[7535]: A57862E4B: from=<fedora@ip-10-65-1 68-165.localdomain>, size=496, nrcpt=1 (queue active) Apr 11 21:23:48 localhost postfix/smtp[7563]: A57862E4B: to=<jschauma@stevens.ed u>, relay=stevens.edu.s9a1.psmtp.com[74.125.148.10]:25, delay=1.2, delays=0.05/0.01/0.18/1, dsn=2.0.0, status=sent (250 Thanks) Apr 11 21:23:48 localhost postfix/qmgr[7535]: A57862E4B: removed

/var/log/maillog CS615 - Aspects of System Administration Slide 4 Receiving... <mail.info>apr 11 17:27:04 panix postfix/smtpd[19962]: connect from na3sys009aog122.obsmtp.com[74.125.149.147] <mail.info>apr 11 17:27:05 panix postfix/smtpd[19962]: NOQUEUE: reject: RCPT from na3sys009aog122.obsmtp.com[74.125.149.147]: 450 4.1.8 <fedora@ip-10-65-168-165.localdomain>: Sender address rejected: Domain not found; from=<fedora@ip-10-65-168-165.localdomain> to=<jschauma@netmeister.org> proto=smtp helo=<na3sys009aog122.obsmtp.com> <mail.info>apr 11 17:27:05 panix postfix/smtpd[19962]: disconnect from na3sys009aog122.obsmtp.com[74.125.149.147]

The Mail System CS615 - Aspects of System Administration Slide 5 Divided into Mail User Agent or MUA, such as mutt, Mail.app, Outlook,... Mail Transfer Agent or MTA, such as postfix, sendmail, qmail,... Mail Delivery Agent or MDA, such as procmail Access Agent providing access via POP, IMAP etc.

Sending email CS615 - Aspects of System Administration Slide 6 Let s try this again... $ ssh linux-lab.cs.stevens.edu $ mail jschauma@stevens.edu Cc: Subject: Act I, Scene I When shall we three meet again? In thunder, lightning, or in rain? ^D $

Sending email CS615 - Aspects of System Administration Slide 7 Let s try this again... $ ssh linux-lab.cs.stevens.edu $ mail jschauma@stevens.edu Cc: Subject: Act I, Scene I When shall we three meet again? In thunder, lightning, or in rain? ^D $ http://shakespeare.mit.edu/macbeth/full.html

Receiving mail CS615 - Aspects of System Administration Slide 8 <mail.info>apr 11 20:22:39 panix postfix/smtpd[313]: connect from na3sys009aog131.obsmtp.com[74.125.149.247] <mail.info>apr 11 20:22:39 panix postfix/smtpd[313]: B4A68356959: client=na3sys009aog131.obsmtp.com[74.125.149.247] <mail.info>apr 11 20:22:40 panix postfix/cleanup[19415]: B4A68356959: message-id=<20150412002232.2d5681460c7@avalon.srcit.stevens-tech.edu> <mail.info>apr 11 20:22:40 panix spamd[15581]: spamd: processing message <20150412002232.2D5681460C7@avalon.srcit.stevens-tech.edu> for spamd:1004 <mail.info>apr 11 20:22:47 panix postfix/qmgr[639]: B4A68356959: removed

Anatomy of an email message CS615 - Aspects of System Administration Slide 9 Date: Sat, 11 Apr 2015 20:22:32-0400 (EDT) From: Jan Schaumann <jschauma@stevens.edu> To: jschauma@stevens.edu Subject: Act I, Scene I X-Mailer: mail (GNU Mailutils 2.2) When shall we three meet again? In thunder, lightning, or in rain?

CS615 - Aspects of System Administration Slide 10 Anatomy of an email message From jschauma@stevens.edu Sat Apr 11 20:22:47 2015 X-Original-To: jschauma@netmeister.org Received: by panix.netmeister.org (Postfix, from userid 1004) id B79633584A3; Sat, 11 Apr 2015 20:22:47-0400 (EDT) Received: from na3sys009aog131.obsmtp.com (na3sys009aog131.obsmtp.com [74.125.149.247]) by panix.netmeister.org (Postfix) with SMTP id B4A68356959 for <jschauma@netmeister.org>; Sat, 11 Apr 2015 20:22:39-0400 (EDT) Received: from warp2.stevens.edu ([155.246.14.17]) by na3sys009aob131.postini.com ([74.125.148.12]) with SMTP ID DSNKVSm6z+EZN/3UM4TuoBFFSQzvUj5B8fMf@postini.com; Sat, 11 Apr 2015 17:22:39 PDT Received: from psmtp.com (na3sys009amx170.postini.com [74.125.149.96]) by warp2.stevens.edu (Postfix) with SMTP id 20F3811FF6B for <jschauma@stevens.edu>; Sat, 11 Apr 2015 20:22:38-0400 (EDT) Received: from na3sys009aog122.obsmtp.com ([74.125.149.147]) by na3sys009amx170.postini.com ([74.125.148.10]) with SMTP; Sun, 12 Apr 2015 00:22:38 GMT Received: from nexus.stevens.edu ([155.246.14.12]) by na3sys009aob122.postini.com ([74.125.148.12]) with SMTP ID DSNKVSm6yA2Ec9zZoknNKL98Cwt6ut+WaT0l@postini.com; Sat, 11 Apr 2015 17:22:38 PDT Received: from avalon.srcit.stevens-tech.edu (nemo.srcit.stevens-tech.edu [155.246.89.102]) by nexus.stevens.edu (Postfix) with ESMTP id 3893D181DB8 for <jschauma@stevens.edu>; Sat, 11 Apr 2015 20:22:32-0400 (EDT) Received: by avalon.srcit.stevens-tech.edu (Postfix, from userid 10235) id 2D5681460C7; Sat, 11 Apr 2015 20:22:32-0400 (EDT) To: <jschauma@stevens.edu> Subject: Act I, Scene I X-Mailer: mail (GNU Mailutils 2.2) Message-Id: <20150412002232.2D5681460C7@avalon.srcit.stevens-tech.edu> Date: Sat, 11 Apr 2015 20:22:32-0400 (EDT) From: jschauma@stevens.edu (Jan Schaumann) Content-Length: 67 Lines: 2 When shall we three meet again? In thunder, lightning, or in rain?

Anatomy of an email message CS615 - Aspects of System Administration Slide 11 An email consists of: mandatory headers (such as From, Delivered-To:,...) optional headers (such as From:, To:, Subject:,...) the (optional) body of the message

Who to hand the mail to? CS615 - Aspects of System Administration Slide 12 $ host -t mx stevens.edu stevens.edu mail is handled by 20 stevens.edu.s9a2.psmtp.com. stevens.edu mail is handled by 30 stevens.edu.s9b1.psmtp.com. stevens.edu mail is handled by 10 stevens.edu.s9a1.psmtp.com. stevens.edu mail is handled by 40 stevens.edu.s9b2.psmtp.com. $

By the way... CS615 - Aspects of System Administration Slide 13 $ whois psmtp.com [...] Registrant Name: DNS Admin Registrant Organization: Google Inc. Registrant Street: 1600 Amphitheatre Parkway Registrant City: Mountain View Registrant State/Province: CA Registrant Postal Code: 94043 Registrant Country: US Registrant Phone: +1.6502530000 Registrant Phone Ext: Registrant Fax: +1.6506188571 [...]

Sending mail... CS615 - Aspects of System Administration Slide 14 $ telnet stevens.edu.s9a1.psmtp.com 25 Trying 74.125.148.10... Connected to stevens.edu.s9a1.psmtp.com. Escape character is ^]. 220 Postini ESMTP 225 y713_pstn_c4 ready. CA Business and Professions Code Section 17538.45 forbids use of this system for unsolicited electronic mail advertisements. helo avalon.srcit.stevens-tech.edu 250 Postini says hello back mail from: <jschauma@stevens.edu> 250 Ok rcpt to: <jschauma@stevens.edu> 250 Ok data 354 Feed me Subject: Act I, Scene I When shall we three meet again? In thunder, lightning, or in rain?. 250 Thanks quit 221 Catch you later Connection closed by foreign host.

SMTP Codes CS615 - Aspects of System Administration Slide 15 SMTP codes consist of three digits in five classes: 1xx Mail server has accepted the command, but does not yet take any action. A confirmation message is required. 2xx Mail server has completed the task successfully without errors. 3xx Mail server has understood the request, but requires further information to complete it. 4xx Mail server has encountered a temporary failure. If the command is repeated without any change, it might be completed. Try again, it may help! 5xx Mail server has encountered a fatal error. Your request can t be processed.

Sending the mail CS615 - Aspects of System Administration Slide 16 IP 166.84.7.99.51845 > 74.125.148.10.25: S 404385236:404385236(0) IP 74.125.148.10.25 > 166.84.7.99.51845: S 1228051958:1228051958(0) ack 404385237 IP 166.84.7.99.51845 > 74.125.148.10.25:. ack 1 IP 74.125.148.10.25 > 166.84.7.99.51845: P 1:170(137) ack 1 IP 166.84.7.99.51845 > 74.125.148.10.25: P 1:28(27) ack 170 IP 74.125.148.10.25 > 166.84.7.99.51845:. ack 28 [...] IP 74.125.148.10.25 > 166.84.7.99.51845:. ack 508 IP 74.125.148.10.25 > 166.84.7.99.51845: P 266:278(12) ack 508 IP 166.84.7.99.51845 > 74.125.148.10.25: P 508:514(6) ack 278 IP 166.84.7.99.51845 > 74.125.148.10.25: F 514:514(0) ack 278 IP 74.125.148.10.25 > 166.84.7.99.51845:. ack 514 IP 74.125.148.10.25 > 166.84.7.99.51845: P 278:299(21) ack 514 IP 74.125.148.10.25 > 166.84.7.99.51845: F 299:299(0) ack 514 IP 74.125.148.10.25 > 166.84.7.99.51845:. ack 515

Receiving the mail CS615 - Aspects of System Administration Slide 17 IP 74.125.149.69.59141 > 166.84.7.99.25: S 1919605344:1919605344(0) IP 166.84.7.99.25 > 74.125.149.69.59141: S 472727490:472727490(0) ack 1919605345 IP 74.125.149.69.59141 > 166.84.7.99.25:. ack 1 IP 166.84.7.99.52290 > 166.84.67.2.53: 10348+ PTR? 69.149.125.74.in-addr.arpa. (44) IP 166.84.67.2.53 > 166.84.7.99.52290: 10348 1/4/4 (227) IP 166.84.7.99.52289 > 166.84.67.2.53: 10349+ AAAA? na3sys009aog102.obsmtp.com. (44) IP 166.84.67.2.53 > 166.84.7.99.52289: 10349 0/1/0 (110) IP 166.84.7.99.52288 > 166.84.67.2.53: 10350+ A? na3sys009aog102.obsmtp.com. (44) IP 166.84.67.2.53 > 166.84.7.99.52288: 10350 1/4/4 (203) IP 166.84.7.99.25 > 74.125.149.69.59141: P 1:41(40) ack 1 IP 74.125.149.69.59141 > 166.84.7.99.25:. ack 41 [...] IP 74.125.149.69.59141 > 166.84.7.99.25: P 71:106(35) ack 81 IP 166.84.7.99.52287 > 166.84.67.2.53: 10351+ A? na3sys009aog102.obsmtp.com. (44) IP 166.84.67.2.53 > 166.84.7.99.52287: 10351 1/4/4 (203) IP 166.84.7.99.52286 > 166.84.67.2.53: 10352+ A? 69.149.125.74.sbl.spamhaus.org. (48)

CS615 - Aspects of System Administration Slide 18 IP 166.84.67.2.53 > 166.84.7.99.52286: 10352 NXDomain 0/1/0 (104) IP 166.84.7.99.52285 > 166.84.67.2.53: 10353+ A? 69.149.125.74.bl.spamcop.net. (46) IP 166.84.67.2.53 > 166.84.7.99.52285: 10353 NXDomain 0/1/0 (99) IP 166.84.7.99.25 > 74.125.149.69.59141: P 81:95(14) ack 106 IP 74.125.149.69.59141 > 166.84.7.99.25:. ack 95 IP 74.125.149.69.59141 > 166.84.7.99.25: P 106:112(6) ack 95 IP 166.84.7.99.25 > 74.125.149.69.59141: P 95:132(37) ack 112 IP 74.125.149.69.59141 > 166.84.7.99.25:. ack 132 IP 74.125.149.69.59141 > 166.84.7.99.25: P 112:1276(1164) ack 132 IP 166.84.7.99.25 > 74.125.149.69.59141:. ack 1276 IP 74.125.149.69.59141 > 166.84.7.99.25: P 1276:1348(72) ack 132 IP 166.84.7.99.25 > 74.125.149.69.59141: P 132:169(37) ack 1348 IP 166.84.7.99.25 > 74.125.149.69.59141: P 169:184(15) ack 1354 IP 166.84.7.99.25 > 74.125.149.69.59141: F 184:184(0) ack 1354 IP 74.125.149.69.59141 > 166.84.7.99.25: F 1354:1354(0) ack 184 IP 166.84.7.99.25 > 74.125.149.69.59141:. ack 1355 IP 74.125.149.69.59141 > 166.84.7.99.25:. ack 185

Service Considerations CS615 - Aspects of System Administration Slide 19 outsourcing versus in-house privacy considerations spam protections phishing protections mail delivery cannons for notifications vs. spam lists high volume traffic demands fine-tuned systems high volume traffic implications on logging See also: http://is.gd/jqp1zm http://is.gd/cxyrwx http://is.gd/o6y5f8

CS615 - Aspects of System Administration Slide 20 Hooray! 5 Minute Break

CS615 - Aspects of System Administration Slide 21 Hypertext Transfer Protocol Today s Universal Internet Pipe

Set up an HTTP server. CS615 - Aspects of System Administration Slide 22 Start an EC2 instance and set up an HTTP server to listen on port 8080. Add a simple index.html file containing your username. When done, paste the full URL (ie http:///) into the class IRC channel #cs615asa. https://webchat.freenode.net/

HTTP: Hypertext CS615 - Aspects of System Administration Slide 23 W W W The World Wide Web is the only thing I know of whose shortened form takes three times longer to say than what it s short for. Douglas Adams

HTTP: Hypertext CS615 - Aspects of System Administration Slide 24 http://is.gd/jnzan6

HTTP CS615 - Aspects of System Administration Slide 25 Hypertext Transfer Protocol RFC2616

HTTP CS615 - Aspects of System Administration Slide 26 HTTP is a request/response protocol.

The Hypertext Transfer Protocol CS615 - Aspects of System Administration Slide 27 HTTP is a request/response protocol: 1. client sends a request to the server 2. server responds

The Hypertext Transfer Protocol CS615 - Aspects of System Administration Slide 28 HTTP is a request/response protocol: 1. client sends a request to the server request method URI protocol version request modifiers client information 2. server responds

CS615 - Aspects of System Administration Slide 29 HTTP: A client request $ telnet www.google.com 80 Trying 173.194.75.147... Connected to www.google.com. Escape character is ^]. GET / HTTP/1.0

The Hypertext Transfer Protocol CS615 - Aspects of System Administration Slide 30 HTTP is a request/response protocol: 1. client sends a request to the server request method URI protocol version request modifiers client information 2. server responds status line (including success or error code) server information entity metainformation content

HTTP: a server response CS615 - Aspects of System Administration Slide 31 HTTP/1.0 200 OK Date: Sun, 31 Mar 2013 01:54:40 GMT Set-Cookie: PREF=ID=c5eb56d629b347cc:FF=0:TM=1364694880:LM=1364694880: S=sIdRFdxV9YvtQOlG; expires=tue, 31-Mar-2015 01:54:40 GMT; path=/; domain=.google.com Set-Cookie: NID=67=hvBnOob2NoZW4haTJVfajbcyn_jips50lKRe-8nawzdCZ6AukNR _s8cnhd6za-z2721na3tplrnxt-2zyiui23j4kdsdf8gg--pmgsmoj3jv5frezqg1elhjv92hl-w2; expires=mon, 30-Sep-2013 01:54:40 GMT; path=/; domain=.google.com; HttpOnly Server: gws <!doctype html><html itemscope="itemscope" itemtype="http://schema.org/webpage"> <head><meta content="search the...

The Hypertext Transfer Protocol CS615 - Aspects of System Administration Slide 32 Server status codes: 1xx Informational; Request received, continuing process 2xx Success; The action was successfully received, understood, and accepted 3xx Redirection; Further action must be taken in order to complete the request 4xx Client Error; The request contains bad syntax or cannot be fulfilled 5xx Server Error; The server failed to fulfill an apparently valid request

HTTP: A client request CS615 - Aspects of System Administration Slide 33 $ telnet www.cs.stevens.edu 80 Trying 155.246.89.84... Escape character is ^]. GET / HTTP/1.0 HTTP/1.1 302 Found Date: Sun, 12 Apr 2015 20:37:23 GMT Server: Apache/2.2.22 (Debian) Location: http://www.stevens.edu/ses/cs Vary: Accept-Encoding Content-Length: 297 Connection: close Content-Type: text/html; charset=iso-8859-1 <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>302 Found</title> </head><body> <h1>found</h1> <p>the document has moved <a href="http://www.stevens.edu/ses/cs">here</a>.</p> <hr> <address>apache/2.2.22 (Debian) Server at www.cs.stevens.edu Port 80</address> </body></html>

HTTP: A client request CS615 - Aspects of System Administration Slide 34 $ telnet www.stevens.edu 80 Trying 54.243.199.233... Connected to mc-4471-1746286150.us-east-1.elb.amazonaws.com. Escape character is ^]. GET /ses/cs HTTP/1.1 Host: www.stevens.edu HTTP/1.1 200 OK Content-Type: text/html; charset=utf-8 Date: Sun, 12 Apr 2015 20:19:58 GMT Last-Modified: Sun, 12 Apr 2015 19:44:48 GMT Server: nginx X-Generator: Drupal 7 (http://drupal.org) X-Request-ID: v-4a62ae68-e151-11e4-bfda-1231381d545c X-Varnish: 1777167175 transfer-encoding: chunked Connection: keep-alive 35e2 <!DOCTYPE html> <html lang="en" dir="ltr"> <head>

HTTP - more than just text CS615 - Aspects of System Administration Slide 35 HTTP is a Transfer Protocol serving data, not any specific text format. Accept-Encoding client header can specify different formats such as gzip, Shared Dictionary Compression over HTTP (SDCH) etc. corresponding server headers: Content-Type and Content-Encoding

HTTP - more than just static data CS615 - Aspects of System Administration Slide 36 HTTP is a Transfer Protocol what is transferred need not be static; resources may generate different data to return based on many variables. CGI resource is executed, needs to generate appropriate response headers server-side scripting (ASP, PHP, Perl,...) client-side scripting (JavaScript/ECMAScript/JScript,...) applications based on HTTP, using: AJAX RESTful services JSON, XML, YAML to represent state and abstract information

HTTP overload CS615 - Aspects of System Administration Slide 37 Ways to mitigate HTTP overload: DNS round-robin to many web servers load balancing web cache / accelerators (reverse proxies) content delivery networks These solutions depend on the location within the network and the scale of the environment.

Load Balancing CS615 - Aspects of System Administration Slide 38

Load Balancing: Inbound CS615 - Aspects of System Administration Slide 39

Load Balancing: Outbound CS615 - Aspects of System Administration Slide 40

Load Balancing: Direct Server Return CS615 - Aspects of System Administration Slide 41

Content Delivery Networks CS615 - Aspects of System Administration Slide 42

Content Delivery Networks CS615 - Aspects of System Administration Slide 43 cache content in strategic locations determine location to serve from via geomapping of IP addresses (beware IPv6 aggregation!) often uses a separate domain to distinguish small objects/large objects or dynamic content/static content either out-sourced or in-house (if your organization is a Tier-1 or Tier-2 peering partner) request routing happens via Global Server Load Balancing, DNS-based request routing, anycasting etc. provides vast amounts of interesting data about your clients (see http://www.akamai.com/stateoftheinternet/)

Reading CS615 - Aspects of System Administration Slide 44 SMTP: http://bit.ly/5ziadj http://is.gd/o6y5f8 RFC 821, 2821 aliases(5), mail(1) sendmail(8), postfix(8)

Reading CS615 - Aspects of System Administration Slide 45 HTTP etc.: RFC 2616, 2818, 3875 http://httpd.apache.org/docs/ http://www.w3.org/protocols/ REST: http://is.gd/lesvga CDNs: http://is.gd/r5doxa http://www.edgecast.com/ https://aws.amazon.com/cloudfront/ http://www.akamai.com/ http://www.limelight.com/... http://developer.yahoo.com/performance/rules.html