Http-Based Proxy Services - AudioCodes Mediant 800 User Manual

CHAPTER 16 Services
HTTP/1.1 200 OK
Access-Control-Allow-Origin: *
Cache-Control: max-age=0
Content-Type: text/html
Date: Thu, 07 Dec 2017 14:35:21 GMT
Server: nginx/1.8.1
Content-Length: 6
Connection: keep-alive
Alice
4. Outgoing SIP message:
INVITE sip:2000@10.7.7.246;user=phone SIP/2.0
Via: SIP/2.0/UDP 10.7.7.246:5060;branch=z9hG4bKac1693897511
Max-Forwards: 70
From: Alice <sip:+15551234567@10.7.2.15;user=phone>;tag=1c1900944531
To: <sip:2000@10.7.7.246;user=phone>
Call-ID: 17651812441120101654@10.7.7.246
CSeq: 1 INVITE
Contact: <sip:1000@10.7.7.246:5060>
Supported: em,100rel,timer,replaces,sdp-anat

HTTP-based Proxy Services

The device can be configured as an HTTP Proxy (or a non-HTTP Proxy) to intermediate between
clients (e.g., HTTP requests) and servers (hosts). The client sends an HTTP GET request
specifying the destination (URL), and the device (acting as an HTTP Proxy), forwards it to the host,
and vice versa.
This feature integrates the NGINX platform, which is an open source proxy server. When you
enable the HTTP Proxy application, the NGINX daemon is launched. When you then configure the
various HTTP Proxy tables, the configuration is reflected in the NGINX configuration file
(nginx.conf). Each parameter has its own NGINX Directive notation syntax, which is shown in the
nginx.conf file. For example, if you have configured an Upstream Host (discussed later in this
section), it is displayed in the NGINX file as "server host:port". You can also configure and apply
additional NGINX Directives that do not have any corresponding parameters in the device's Web
interface. For more information, see
The device supports the following proxy services:
■ HTTP Reverse Proxy for managing equipment behind NAT: You can configure the
device to function as a Reverse HTTP Proxy server. You can use this for many HTTP-based
applications. For example, you can use it to intermediate between REST API clients and a
REST server.
Mediant 800 Gateway & E-SBC | User's Manual
Configuring HTTP Directive Sets
- 271 -
on page 286.