...http://192.168.0.2/alert-receiver.cgi?$time&$name and produce an email alert? I have a bit of access control hardware that can be configured to send out an http alert to a specific url, and I want to convert this into a email alert, but I don't know how to write a script that will interpret an http message.
I have tried a simple sendmail.php script on some webspace I control, (setting the http alert to http://mydomain.com/sendmail.php) but the hardware doesn't actually browse there, all it does is send an http message (an example of which is in the question) so the php doesn't send the mail. Other token strings include $door-name and $timezone.
Any guidance would be welcome.
The user guide for the hardware reads as follows:
HTTP messages may be constructed that include relevant data that are related to the event triggering
the message. This data is referred to as "parameter substitution" in this help document. All
events do not include the same set of data. See the following table for the parameters that are
available with each type of event.
When an HTTP alert is generated, additional Edge Solo system generated information can be incorporated
into the message configured by the installer. Examples would include the time the alert
was generated or information about the cardholder that triggered the alert. This dynamic content
is specified using a special Token String that the installer configures as part of the HTTP message.
For example, http://192.168.0.2/alert-receiver.cgi?$time&$lastname would send the time
and cardholder last name, when available, for all events that were configured to send that URL.
I have tried a simple sendmail.php script on some webspace I control, (setting the http alert to http://mydomain.com/sendmail.php) but the hardware doesn't actually browse there, all it does is send an http message (an example of which is in the question) so the php doesn't send the mail. Other token strings include $door-name and $timezone.
Any guidance would be welcome.
The user guide for the hardware reads as follows:
HTTP messages may be constructed that include relevant data that are related to the event triggering
the message. This data is referred to as "parameter substitution" in this help document. All
events do not include the same set of data. See the following table for the parameters that are
available with each type of event.
When an HTTP alert is generated, additional Edge Solo system generated information can be incorporated
into the message configured by the installer. Examples would include the time the alert
was generated or information about the cardholder that triggered the alert. This dynamic content
is specified using a special Token String that the installer configures as part of the HTTP message.
For example, http://192.168.0.2/alert-receiver.cgi?$time&$lastname would send the time
and cardholder last name, when available, for all events that were configured to send that URL.