Hurra Proxy

Hurra Proxy This is the FAQ for HurraProxy solution. All entries are assumed to be relevant to The Apache HTTP Server, unless otherwise noted. Direct further questions to our Account Manager.

30/04/2013 # HurraProxy FAQ # Page 1

Table of contents: 1. 2. 3. 4.

What is a config file? How does the config file work? Is it dangerous for the client server? Does the config file give Hurra access to the customer's server?

30/04/2013 # HurraProxy FAQ # Page 2

1. What is a config file? It is very important for our SEO product that our SEO solution is visible for Google and users as if it comes from the customer's domain so it's perceived as part of the customer's site, not a Hurra site. The config file enables this essential functionality of our SEO solution. All template pages are stored on our servers, but are visible to the outside world over the customer's domain. Storing content on our servers gives us full control of the solution - we can perform updates transparently, implement new features and optimize on daily basis without requiring any action from the customer. It's very important not to modify any response from our server, all error pages and redirects should be served by Hurra's server

30.04.2013 # HurraProxy FAQ # Page 3

2. How does the config file work? The config file usually consists of two parts. The first part loads required modules (if not loaded yet). These modules are available in Apache distribution by default but could have been changed by your system administrator during compilation (ask him to add them if they have been deactivated). Comprehensive documentation for these modules can be found on Apache's project site. # Proxy and rewrites modules activate - when they're not yet loaded # Warning: change /usr/lib/httpd/modules/ to your modules path LoadModule LoadModule

rewrite_module proxy_http_module

/usr/lib/httpd/modules/mod_rewrite.so /usr/lib/httpd/modules/proxy_http.so

### Uncomment following line in case of Apache 1.3 Server # LoadModule proxy_module /usr/lib/httpd/modules/mod_proxy.so ### Uncomment following lie in case of Apache 2.2 Server #LoadModule proxy_module /usr/lib/httpd/modules/mod_proxy.so #LoadModule proxy_http_module /usr/lib/httpd/modules/mod_proxy_http.so


How does the config file work? - continued. The second part contains the rules needed to achieve the required functionality (so the content appears to come from the customer, not Hurra) RewriteEngine On RewriteRule ^/?catalog$ http://www.customer.com/catalog/ [R=301,L] RewriteRule ^/?catalog/_im1/(.+)$ http://img1.customer.com/$1 [P,NE,L] RewriteRule ^/?catalog/_im2/(.+)$ http://img2.customer.com/$1 [P,NE,L] RewriteRule ^/?catalog/(.*)$ http://customer.hurraproxy.com/catalog/$1 [P,NE,L]

The second part is highly customer-dependant so the rule-set sent to you can vary slightly. The above example only introduces basic concept.


3. Is it dangerous for the client server? In general the answer is no. By default, access to the proxy is limited to localhost which is all that is required. However, this could be changed by a system administrator (proxy directive) leading to your server acting as an open proxy, which would be unwanted in most cases. Our suggestion would be to ask the system administrator to check the proxy directives and make sure that access to the proxy is only authorized from fixed locations.


4. Does the config file give Hurra access to the customer's server? No, the config file doesn't grant access to the customer's server in any way.
