HTTP server
GnGSmS standard package comes with a "Web Server" service which
enables receiving SMS messages over over
Http protocol.
GnGSmS web server is configurable via the user interface, you can
customized according to your SMS provider request parameters.
Like all other GnGSmS services you can create multiple web
servers in one GnGSmS instance, GnGSmS doesn't force a limit to the
number of web servers you can create, this is of course dependent on
the hardware.
Under the hoods GnGSmS utilizes the excellent Java web server
Jetty to handle HTTP requests.
Service Name
|
The name of this service, it is better
to have a unique name for each service in a GnGSmS
configuration |
Service Description
|
A short description of the service |
Disabled
|
Enable or disable this service, if
disabled the service will not start when you start the
GnGSmS services |
Enable GET
|
whether to enable or disable GET http
requests |
Enable POST
|
Whether to enable or disable POST http
requests |
From
|
The HTTP parameter of the message
Sender number/name |
To
|
The HTTP parameter of the message
reciever number/name |
Text
|
The HTTP parameter of the message text
|
Validate
|
Whether SMS parameters should be
validated, if enabled the request will not be processed
unless it contains the from/to/text parameters |
Include all parameters
|
If this option is
selected then all request parameters will be added to
the request context
and will be available to the
action
tree. Example:
Consider an http request that contains a parameter named
USER, suppose for one request the value of USER was
"myuser". for this paramater GnGSmS
context variable will be created with the name USER,
which is accessible in the
action tree as
${USER}. |
port
|
Server port to listen to |
Context
|
The HTTP path context,
this is the part of the URL that comes after the server name
and port. Example: For a URL
like Http://host:8080/receieve?from=1234&to=......
The context is "receive"
|
Statistics
|
Whether to collect requests statistics
(Still to come) |
