Content Server Reverse Proxy Server Resource Guide

Total Page:16

File Type:pdf, Size:1020Kb

Content Server Reverse Proxy Server Resource Guide Cover Page Content Server - Reverse Proxy Server Resource Guide 10g Release 3 (10.1.3.3.0) March 2007 Content Server - Reverse Proxy Server Resource Guide, 10g Release 3 (10.1.3.3.0) Copyright © 2007, Oracle. All rights reserved. Contributing Authors: Sandra Christiansen The Programs (which include both the software and documentation) contain proprietary information; they are provided under a license agreement containing restrictions on use and disclosure and are also protected by copyright, patent, and other intellectual and industrial property laws. Reverse engineering, disassembly, or decompilation of the Programs, except to the extent required to obtain interoperability with other independently created software or as specified by law, is prohibited. The information contained in this document is subject to change without notice. If you find any problems in the documentation, please report them to us in writing. This document is not warranted to be error-free. Except as may be expressly permitted in your license agreement for these Programs, no part of these Programs may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose. If the Programs are delivered to the United States Government or anyone licensing or using the Programs on behalf of the United States Government, the following notice is applicable: U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are "commercial computer software" or "commercial technical data" pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, use, duplication, disclosure, modification, and adaptation of the Programs, including documentation and technical data, shall be subject to the licensing restrictions set forth in the applicable Oracle license agreement, and, to the extent applicable, the additional rights set forth in FAR 52.227-19, Commercial Computer Software--Restricted Rights (June 1987). Oracle USA, Inc., 500 Oracle Parkway, Redwood City, CA 94065. The Programs are not intended for use in any nuclear, aviation, mass transit, medical, or other inherently dangerous applications. It shall be the licensee's responsibility to take all appropriate fail-safe, backup, redundancy and other measures to ensure the safe use of such applications if the Programs are used for such purposes, and we disclaim liability for any damages caused by such use of the Programs. Oracle, JD Edwards, PeopleSoft, and Siebel are registered trademarks of Oracle Corporation and/or its affiliates. Other names may be trademarks of their respective owners. The Programs may provide links to Web sites and access to content, products, and services from third parties. Oracle is not responsible for the availability of, or any content provided on, third-party Web sites. You bear all risks associated with the use of such content. If you choose to purchase any products or services from a third party, the relationship is directly between you and the third party. Oracle is not responsible for: (a) the quality of third- party products or services; or (b) fulfilling any of the terms of the agreement with the third party, including delivery of products or services and warranty obligations related to purchased products or services. Oracle is not responsible for any loss or damage of any sort that you may incur from dealing with any third party. Table of Contents Chapter 1: Introduction About Content Delivery . .1-1 Dynamic Delivery of Content . .1-2 Static Delivery of Content . .1-2 Dynamic and Static Delivery . .1-2 About Proxy Caching . .1-3 Advantages and Disadvantages . .1-4 About Hierarchical Cache Systems . .1-5 Reverse Proxy Considerations. .1-6 Using the 8.3 Naming Convention . .1-6 Defining Port Assignments . .1-6 Site Studio and Firewall Considerations . .1-7 About This Guide . .1-7 Audience . .1-7 Conventions. .1-7 Document Organization . .1-8 Additional Documentation . .1-9 Chapter 2: Using Squid Obtaining and Installing Squid . .2-1 Installing Squid on UNIX . .2-1 Installing Squid on Microsoft Windows . .2-2 Configuration Options for Squid . .2-3 Basic Configuration Options . .2-3 Configuration for Dynamic Server Pages . .2-3 Configuring for Reverse Proxy. .2-4 Purging Objects from the Squid Cache . .2-5 Sample squid.conf file . .2-5 Starting Squid. .2-6 Content Server - Reverse Proxy Server Resource Guide iii Table of Contents Verifying and Tuning System Performance . .2-6 Testing Squid. .2-6 Setting Refresh Properties. .2-7 Disabling Proxy Caching . .2-7 Chapter 3: Using Microsoft ISA Server Pre-Installation Considerations . .3-1 Multi-Networking . .3-1 Terms and Concepts . .3-2 Caching . .3-3 Users and Privileges . .3-3 Obtaining Microsoft ISA . .3-4 Installing Microsoft ISA. .3-4 Verifying and Tuning System Performance . .3-4 Verifying System Performance . .3-5 Setting the Refresh Rate . .3-5 Disabling Caching . .3-5 Chapter 4: Using Sun Java System Obtaining Sun Java System. .4-1 Installing Sun Java System . .4-2 Installing on Microsoft Systems . .4-2 Installing on UNIX Systems . .4-3 Installing Additional Proxy Servers. .4-4 Setting Up a Reverse Proxy Server . .4-5 Setting Up A Reverse Proxy . .4-5 Additional Notes . .4-6 Verifying and Tuning System Performance . .4-7 Verifying System Performance . .4-7 Monitoring with Log Files. .4-7 Other Monitoring Methods. .4-7 Setting the Refresh Rate . .4-8 Disabling Caching . .4-8 Chapter 5: Proxy Considerations with Site Studio Site Studio Design Considerations. .5-1 Configuring Site Studio . .5-1 iv Content Server - Reverse Proxy Server Resource Guide Table of Contents Site Studio Designer Changes. .5-1 Changes for Versions Prior to 7.5 . .5-2 Content Server Changes . .5-7 Host Web Server Changes . .5-7 Configuring the ssBaseServerAddress Variable . .5-8 Older Versions of Site Studio (pre-7.2.1) . .5-8 Chapter 6: Tips and Tricks Squid . .6-1 Squid and Site Studio . .6-1 Setting Appropriate Directory Permissions . .6-1 Setting File Descriptor Limits . .6-2 Using Swap Directories . .6-2 Querying Other Cache Servers . .6-2 Controlling Which Pages are Cached . .6-3 Microsoft ISA . .6-3 Using Windows Media Series . .6-3 Network Adapters . .6-3 Caching Considerations. .6-3 Setting Cache Parameters. .6-4 Sun Java System Web Proxy Server . .6-4 Up-To-Date Checks . .6-4 Proxy Timeouts and CGI Scripts . .6-5 Caching Pages Requiring User Authentication . .6-5.
Recommended publications
  • Updating Systems and Adding Software in Oracle® Solaris 11.4
    Updating Systems and Adding Software ® in Oracle Solaris 11.4 Part No: E60979 November 2020 Updating Systems and Adding Software in Oracle Solaris 11.4 Part No: E60979 Copyright © 2007, 2020, Oracle and/or its affiliates. License Restrictions Warranty/Consequential Damages Disclaimer This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited. Warranty Disclaimer The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing. Restricted Rights Notice If this is software or related documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, then the following notice is applicable: U.S. GOVERNMENT END USERS: Oracle programs (including any operating system, integrated software, any programs embedded, installed or activated on delivered hardware, and modifications of such programs) and Oracle computer documentation or other Oracle data delivered to or accessed by U.S. Government end users are "commercial
    [Show full text]
  • Load Balancing for Heterogeneous Web Servers
    Load Balancing for Heterogeneous Web Servers Adam Pi´orkowski1, Aleksander Kempny2, Adrian Hajduk1, and Jacek Strzelczyk1 1 Department of Geoinfomatics and Applied Computer Science, AGH University of Science and Technology, Cracow, Poland {adam.piorkowski,jacek.strzelczyk}@agh.edu.pl http://www.agh.edu.pl 2 Adult Congenital and Valvular Heart Disease Center University of Muenster, Muenster, Germany [email protected] http://www.ukmuenster.de Abstract. A load balancing issue for heterogeneous web servers is de- scribed in this article. The review of algorithms and solutions is shown. The selected Internet service for on-line echocardiography training is presented. The independence of simultaneous requests for this server is proved. Results of experimental tests are presented3. Key words: load balancing, scalability, web server, minimum response time, throughput, on-line simulator 1 Introduction Modern web servers can handle millions of queries, although the performance of a single node is limited. Performance can be continuously increased, if the services are designed so that they can be scaled. The concept of scalability is closely related to load balancing. This technique has been used since the beginning of the first distributed systems, including rich client architecture. Most of the complex web systems use load balancing to improve performance, availability and security [1{4]. 2 Load Balancing in Cluster of web servers Clustering of web servers is a method of constructing scalable Internet services. The basic idea behind the construction of such a service is to set the relay server 3 This is the accepted version of: Piorkowski, A., Kempny, A., Hajduk, A., Strzelczyk, J.: Load Balancing for Heterogeneous Web Servers.
    [Show full text]
  • Enabling HTTP/2 on an IBM® Lotus Domino® Server
    Enabling HTTP/2 on an IBM® Lotus Domino® Server Setup Guide Alex Elliott © AGECOM 2019 https://www.agecom.com.au CONTENTS Introduction ..................................................................................................................................................... 3 Requirements .................................................................................................................................................. 3 About HTTP/2 ................................................................................................................................................. 3 About NGINX .................................................................................................................................................. 3 How this works ................................................................................................................................................ 4 Step 1 – Install NGINX .................................................................................................................................... 5 Step 2 – Setting up NGINX to run as a Windows Service ............................................................................... 6 Step 3 – Update Windows Hosts File .............................................................................................................. 8 Step 4 – Add another local IP Address ........................................................................................................... 8 Step 5 - Creating SSL Certificate Files
    [Show full text]
  • Application of GPU for High-Performance Network Processing
    SSLShader: Cheap SSL Acceleration with Commodity Processors Keon Jang+, Sangjin Han+, Seungyeop Han*, Sue Moon+, and KyoungSoo Park+ KAIST+ and University of Washington* 1 Security of Paper Submission Websites 2 Network and Distributed System Security Symposium Security Threats in the Internet . Public WiFi without encryption • Easy target that requires almost no effort . Deep packet inspection by governments • Used for censorship • In the name of national security . NebuAd’s targeted advertisement • Modify user’s Web traffic in the middle 3 Secure Sockets Layer (SSL) . A de-facto standard for secure communication • Authentication, Confidentiality, Content integrity Client Server TCP handshake Key exchange using public key algorithm Server (e.g., RSA) identification Encrypted data 4 SSL Deployment Status . Most of Web-sites are not SSL-protected • Less than 0.5% • [NETCRAFT Survey Jan ‘09] . Why is SSL not ubiquitous? • Small sites: lack of recognition, manageability, etc. • Large sites: cost • SSL requires lots of computation power 5 SSL Computation Overhead . Performance overhead (HTTPS vs. HTTP) • Connection setup 22x • Data transfer 50x . Good privacy is expensive • More servers • H/W SSL accelerators . Our suggestion: • Offload SSL computation to GPU 6 SSLShader . SSL-accelerator leveraging GPU • High-performance • Cost-effective . SSL reverse proxy • No modification on existing servers Web Server SMTP Server SSLShader POP3 Server SSL-encrypted session Plain TCP 7 Our Contributions . GPU cryptography optimization • The fastest RSA
    [Show full text]
  • Linux Tips and Tricks
    Linux Tips and Tricks Chris Karakas Linux Tips and Tricks by Chris Karakas This is a collection of various tips and tricks around Linux. Since they don't fit anywhere else, they are presented here in a more or less loose form. We start on how to get an attractive vi by using syntax highlighting, multiple search and the smartcase, incsearch, scrolloff, wildmode options in the vimrc file. We continue on various configuration subjects regarding Netscape, like positioning and sizing of windows and roaming profiles. Further on, I present a CSS file for HTML documents that were created automatically from DocBook SGML. Also a chapter on transparent proxying with Squid. Copyright © 2002-2003 Chris Karakas. Permission is granted to copy, distribute and/or modify this docu- ment under the terms of the GNU Free Documentation License, Version 1.1 or any later version published by the Free Software Foundation; with no Invariant Sections, with no Front-Cover Texts, and with no Back-Cover Texts. A copy of the license can be found at the Free Software Foundation. Revision History Revision 0.04 04.06..2003 Revised by: CK Added chapter on transparent proxying. Added Index. Alt text and captions for images Revision 0.03 29.05.2003 Revised by: CK Added chapters on Netscape and CSS for DocBook. Revision 0.02 18.12.2002 Revised by: CK first version Table of Contents 1. Introduction......................................................................................................... 1 1.1. Disclaimer .....................................................................................................................1
    [Show full text]
  • The Squid Caching Proxy
    The Squid caching proxy Chris Wichura [email protected] What is Squid? • A caching proxy for – HTTP, HTTPS (tunnel only) –FTP – Gopher – WAIS (requires additional software) – WHOIS (Squid version 2 only) • Supports transparent proxying • Supports proxy hierarchies (ICP protocol) • Squid is not an origin server! Other proxies • Free-ware – Apache 1.2+ proxy support (abysmally bad!) • Commercial – Netscape Proxy – Microsoft Proxy Server – NetAppliance’s NetCache (shares some code history with Squid in the distant past) – CacheFlow (http://www.cacheflow.com/) – Cisco Cache Engine What is a proxy? • Firewall device; internal users communicate with the proxy, which in turn talks to the big bad Internet – Gate private address space (RFC 1918) into publicly routable address space • Allows one to implement policy – Restrict who can access the Internet – Restrict what sites users can access – Provides detailed logs of user activity What is a caching proxy? • Stores a local copy of objects fetched – Subsequent accesses by other users in the organization are served from the local cache, rather than the origin server – Reduces network bandwidth – Users experience faster web access How proxies work (configuration) • User configures web browser to use proxy instead of connecting directly to origin servers – Manual configuration for older PC based browsers, and many UNIX browsers (e.g., Lynx) – Proxy auto-configuration file for Netscape 2.x+ or Internet Explorer 4.x+ • Far more flexible caching policy • Simplifies user configuration, help desk support,
    [Show full text]
  • Installation Guide Supplement for Use with Squid Web Proxy Cache (WWS
    Installation Guide Supplement for use with Squid Web Proxy Cache Websense® Web Security Websense Web Filter v7.5 ©1996 - 2010, Websense, Inc. 10240 Sorrento Valley Rd., San Diego, CA 92121, USA All rights reserved. Published 2010 Printed in the United States of America and Ireland The products and/or methods of use described in this document are covered by U.S. Patent Numbers 5,983,270; 6,606,659; 6,947,985; 7,185,015; 7,194,464 and RE40,187 and other patents pending. This document may not, in whole or in part, be copied, photocopied, reproduced, translated, or reduced to any electronic medium or machine- readable form without prior consent in writing from Websense, Inc. Every effort has been made to ensure the accuracy of this manual. However, Websense, Inc., makes no warranties with respect to this documentation and disclaims any implied warranties of merchantability and fitness for a particular purpose. Websense, Inc., shall not be liable for any error or for incidental or consequential damages in connection with the furnishing, performance, or use of this manual or the examples herein. The information in this documentation is subject to change without notice. Trademarks Websense is a registered trademark of Websense, Inc., in the United States and certain international markets. Websense has numerous other unregistered trademarks in the United States and internationally. All other trademarks are the property of their respective owners. Microsoft, Windows, Windows NT, Windows Server, and Active Directory are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries. Red Hat is a registered trademark of Red Hat, Inc., in the United States and other countries.
    [Show full text]
  • Running SQUID In
    Running SQUIDSQUID in freeBSD Sufi Faruq Ibne Abubakar AKTEL, TMIB What is ? • A full-featured Web proxy cache • Designed to run on Unix systems • Free, open-source software • The result of many contributions by unpaid (and paid) volunteers Why will I use ? • Save 30% Internet Bandwidth • Access Control • Low cost proxy • Proxy keeps database of each request comes from client • Proxy itself goes to get resource from internet to satisfy first time request • Proxy caches resources immediately after obtaining it from internet. • Proxy serves the resource from cache in second request for same resources Consideration for deployment • User calculation • System Memory (Min 256 MB RAM) • Speedy Storage (SCSI Preferred) •Faster CPU • Functionality expectations Supports • Proxying and caching of HTTP, FTP, and other URLs • Proxying for SSL • Cache hierarchies • ICP, HTCP, CARP, Cache Digests • Transparent caching • WCCP (Squid v2.3 and above) • Extensive access controls • HTTP server acceleration • SNMP • caching of DNS lookups Obtaining • Obtain package source from: – http://www.squid-cache.org – Squid Mirror Sites (http://www.squid- cache.org/Mirrors/http-mirrors.html) – Binary download for FreeBSD also available (http://www.squid-cache.org/binaries.html) • “STABLE” releases, suitable for production use • “PRE” releases, suitable for testing Installing • tar zxvf squid-2.4.STABLE6-src.tar.gz • cd squid-2.4.STABLE6 • ./configure --enable-removal-policies --enable-delay-pools --enable-ipf-transparent --enable-snmp --enable-storeio=diskd,ufs --enable-storeio=diskd,ufs
    [Show full text]
  • The Security Considerations with Squid Proxy Server for Windows
    International Journal of Engineering Research & Technology (IJERT) ISSN: 2278-0181 Vol. 2 Issue 12, December - 2013 The Security Considerations with Squid Proxy Server for Windows Mr.E.Srinivasa Rao 1, Mr.B.Srinu 2 1M.Tech (SE) of IT Department, Gayathri Vidya Parishad College of Engineering, Visakhapatnam. 2Asst.Professor of IT Department, Gayathri Vidya Parishad College of Engineering, Visakhapatnam. Abstract INTRODUCTION Securing and controlling workstation access to the Squid is a Unix-based proxy server that caches web has never been an easy task for security Internet content closer to a requestor than its professionals. Firewalls and access control list on original point of origin. Squid supports caching of routers alone may not bring an acceptable level of many different kinds of Web objects, including security for your organization. Even if their those accessed through HTTP and FTP. Caching primary role is to reduce network traffic and frequently requested Web pages, media files and improve performance, HTTP proxy servers (also other content accelerates response time and called cache servers) are likely to be installed as reduces bandwidth congestion. A Squid proxy an additional security layer and as a web surfing server is generally installed on a separate server monitoring system. Having secure proxy servers is than the Web server with the original files. Squid critical because many users depend on it for their works by tracking object use over the network. work. Several proxy server products are available Squid will initially act as an intermediary, simply nowadays. Since commercial products are very IJERTpassing the client's request on to the server and expensive, alternative products such as openIJERT saving a copy of the requested object.
    [Show full text]
  • Introduction
    HTTP Request Smuggling in 2020 – New Variants, New Defenses and New Challenges Amit Klein SafeBreach Labs Introduction HTTP Request Smuggling (AKA HTTP Desyncing) is an attack technique that exploits different interpretations of a stream of non-standard HTTP requests among various HTTP devices between the client (attacker) and the server (including the server itself). Specifically, the attacker manipulates the way various HTTP devices split the stream into individual HTTP requests. By doing this, the attacker can “smuggle” a malicious HTTP request through an HTTP device to the server abusing the discrepancy in the interpretation of the stream of requests and desyncing between the server’s view of the HTTP request (and response) stream and the intermediary HTTP device’s view of these streams. In this way, for example, the malicious HTTP request can be "smuggled" as a part of the previous HTTP request. HTTP Request Smuggling was invented in 2005, and recently, additional research cropped up. This research field is still not fully explored, especially when considering open source defense systems such as mod_security’s community rule-set (CRS). These HTTP Request Smuggling defenses are rudimentary and not always effective. My Contribution My contribution is three-fold. I explore new attacks and defense mechanisms, and I provide some “challenges”. 1. New attacks: I provide some new HTTP Request Smuggling variants and show how they work against various proxy-server (or proxy-proxy) combinations. I also found a bypass for mod_security CRS (assuming HTTP Request Smuggling is possible without it). An attack demonstration script implementing my payloads is available in SafeBreach Labs’ GitHub repository (https://github.com/SafeBreach-Labs/HRS).
    [Show full text]
  • Responsibly Intercepting TLS and the Impact of TLS 1.3
    TECHNICAL BRIEF Responsibly Intercepting TLS and the Impact of TLS 1.3 Author: Roelof Du Toit The focus of this paper will be active TLS intercept with TLS client Introduction endpoint configuration – commonly found in antivirus products TLS is an inherently complex protocol due to the specialized and middlebox (TLS relay, forward proxy, NGFW, and more) knowledge required to implement and deploy it correctly. TLS stack deployments. Although it is not the focus, many of the principles in developers must be well versed in applied cryptography, secure this paper also apply to TLS offload deployments, where “offload” programming, IETF and other standards, application protocols, is referring to the stripping of the TLS layer before forwarding the and network security in general. Application developers using traffic, e.g., HTTPS to HTTP (a.k.a. reverse proxy deployments). The TLS should have the same qualities; especially if the application is paper assumes a basic knowledge of TLS, as well as the concept of TLS intercept. Throw government regulations, unique customer TLS intercept using an emulated X.509 certificate. requirements, misbehaving legacy endpoints, and performance requirements into the mix, and it soon becomes clear that mature systems engineering skills and strong attention to detail are Responsible TLS Intercept prerequisites to building a reliable and trustworthy TLS intercept Cryptography is harder than it looks, and TLS intercept is complex. solution. Paraphrasing Bruce Schneier: security requires special Vendors of security products must act responsibly in general but design considerations because functionality does not equal quality1. should take extra care during the development of TLS intercept The goal of this paper is to contribute to the security community applications.
    [Show full text]
  • Nginx Reverse Proxy Certificate Authentication
    Nginx Reverse Proxy Certificate Authentication Gnomic Cy outdate, his digamma court-martials depurate ungovernably. Rod usually oughts indirectly or glories orbicularly when mulish Tremain outrun subversively and disingenuously. Intelligential and well-made Thebault still blaze his paraffine poutingly. Keycloak authenticates the user then asks the user for consent to grant access to the client requesting it. HTTP server application, the same techniques as used for Apache can be applied. SSL traffic over to SSL. Connect to the instance and install NGINX. Next the flow looks at the Kerberos execution. Similar requirements may be required for your environment and reverse proxy if not using NGINX. The Octopus Deploy UI is stateless; round robin should work without issues. If a certificate was not present. Once we are done with it, it can be useful to use hardcoded audience. CA under trusted root certificates. Encrypt registration to complete. The only part of Keycloak that really falls into CSRF is the user account management pages. Attract and empower an ecosystem of developers and partners. If this is set and no password is provided then a service account user will be created. If your unique circumstances require you to avoid storing secrets inside a configuration file, a working Mirth installation, sign up to our newsletter. Keycloak is a separate server that you manage on your network. SFTP public key authentication on MFT Server before, such as clients acting locally on the Tamr server. What we have not done is specify which users the admin is allowed to map this role too. Java Web Service Authentication Soap Header.
    [Show full text]