Your SlideShare is downloading. ×
Introduction server Construction
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Introducing the official SlideShare app

Stunning, full-screen experience for iPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Introduction server Construction

2,557
views

Published on

신입생들을 위한 길라잡이 세미나입니다. …

신입생들을 위한 길라잡이 세미나입니다.

서버구축관련 20기 왕찡위.

Published in: Education

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
2,557
On Slideshare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
23
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. WEB SERVERS Hanulso 23 기 왕찡위
  • 2. WEB SERVERS (IIS AND APACHE)
    • Outline
    • Introduction
    • 2 HTTP Request Types
    • 3 System Architecture
    • 4 Client-Side Scripting versus Server-Side Scripting
    • 5 Accessing Web Servers
    • 6 Microsoft Internet Information Services (IIS)
    • 6.1 Microsoft Internet Information Services (IIS) 6.0
    • 6.2 Microsoft Internet Information Services (IIS) 7.0
    • 7 Apache Web Server
    • 8 Requesting Documents
    • 8.1 XHTML
    • 8.2 ASP.NET
    • 8.3 PHP
    • 9 Web Resources
  • 3. OBJECTIVES
      • To understand a Web server’s functionality.
      • To introduce Apache Web server.
      • To learn how to request documents from a Web server.
  • 4. 1  INTRODUCTION
    • Web server
      • Responds to client requests by providing resources
    • URI (Uniform Resource Identifier)
    • Web server and client communicate with platform-independent Hypertext Transfer Protocol (HTTP)
  • 5. 1  INTRODUCTION
  • 6. WEB SERVER ARCHITECTURE
  • 7. HOW THE WWW WORKS
  • 8. DOMAIN NAME SERVER SYSTEM
  • 9. EXAMPLE OF AN HTTP REQUEST FROM A WEB BROWSER GET http://www.kelley.indiana.edu/ardennis/home.htm HTTP/1.1 Date: Mon 06 Aug 2008 17:35:46 GMT User-Agent: Mozilla/6.0 Referer: http://www.indiana.edu/~aisdept/faculty.htm Request Header ]- Request Line ]- Web browser (this is Netscape) Command URL HTTP version URL that contained the link to the requested URL
  • 10. HTTP RESPONSE FROM A WEB SERVER
    • HTTP/1.1 200 OK ]- Response Status
    • Date: Mon 06 Aug 2008 17:35:46 GMT ]- Date
    • Server: NCSA/1.3 ]- Web server
    • Location: http:// www.kelley.indiana.edu/adennis/home.htm ]- URL
    • Content-type: text/html ]- Type of file
    • <html>
    • <head>
    • <title>Allen R. Dennis</title>
    • </head>
    • <body>
    • <H2> Allen R. Dennis </H2>
    • <P>Welcome to the home page of Allen R. Dennis</P>
    • </body>
    • </html>
    HTTP version Status code Reason Response Header Response Body
  • 11. 2  HTTP REQUEST TYPES
    • GET (default) and POST do basically the same thing: Send data from the client to the server. However, they have some differences:
    • GET
      • Appends form data directly to the end of the URL —visible to users (not suitable for sending passwords)
      • Limited to 2,048 characters for the entire URL
      • Result page can be bookmarked and cached
    • POST
      • Sends form data in the HTTP request—invisible to users
      • Virtually no limit (but check your specific configuration)
      • Results are not cacheable or bookmarkable
  • 12. 3  SYSTEM ARCHITECTURE
    • Multi-tier application ( n -tier application)
      • Information tier (data or bottom tier)
        • Maintains data for the application
        • Stores data in a relational database management system (RDBMS)
      • Middle tier
        • Implements business logic and presentation logic
        • Control interactions between application clients and application data
      • Client tier (top tier)
        • Application’s user interface
        • Users interact directly with the application through the client tier
  • 13. N-TIER CLIENT-SERVER ARCHITECTURE
  • 14. 4  CLIENT-SIDE SCRIPTING VERSUS SERVER-SIDE SCRIPTING
    • Client-side scripts
      • Validate user input
        • Reduce requests needed to be passed to server
        • Access browser
        • Enhance Web pages with DHTML, ActiveX controls, and applets
    • Server-side scripts
      • Executed on server
      • Generate custom response for clients
      • Wide range of programmatic capabilities
      • Access to server-side software that extends server functionality
  • 15. INSTALLING A WEB SERVER
  • 16. HOSTING A WEBSITE: SELF HOSTING
    • Install a web server on a computer
    • Local access
      • Using domain <localhost>
      • or IP address 127.0.0.1
      • Necessary for server-side programming development
    • Global access
      • Register a human-readable domain name
      • Obtain IP address
        • Static: Costs more
        • Dynamic: Needs dynamic DNS system, e.g. http://www.dyndns.com/
  • 17. HOSTING A WEBSITE: HOSTING SERVICE
    • Register a domain name
      • Assign name servers
      • Host takes care of IP addressing
    • Develop website locally
    • Upload website via FTP for global access
      • E.g. Filezilla
  • 18. WEB SERVER ARCHITECTURE
    • LAMP: Most popular—fully open source
      • Linux for operating system
      • Apache for web server
      • MySQL for database
      • PHP for server-side scripting
    • Others:
      • WAMP: Uses Windows for operating system, with Apache, MySQL, and PHP
      • WISA: Full Microsoft package
        • Windows
        • Internet Information Server (IIS)
        • SQL Server (enterprise) or Access (small-scale)
        • ASP or ASP.NET
  • 19. 7  APACHE WEB SERVER
    • Currently the most popular Web server
    • Stability
    • Efficiency
    • Portability
    • Open-source
  • 20. ALL-IN-ONE APACHE/MYSQL/PHP PACKAGES
    • APMSETUP (recommended)
      • Includes PHPMyAdmin for administering MySQL database
      • Installation and configuration
    • AbriaSoft Merlin Desktop Edition
      • Includes PHPMyAdmin
    • WAMP Server
    • PHP Triad
  • 21. REQUESTING XHTML OR PHP DOCUMENTS
    • Request PHP documents from Apache
    • Save PHP documents in the www folder for EasyPHP ( htdocs is the default Apache folder name)
    • Launch web browser
      • With EasyPHP, right-click on the status bar icon and click “Local Web”
    • Enter PHP document’s location in Address field, starting with http://localhost/ or http://127.0.0.1/
  • 22. 8.1 XHTML AND PHP Fig. 21.15 Requesting test.html from IIS 6 or Apache. Fig. 21.23 Requesting test.php from Apache.
  • 23. THANK YOU