URL contact settings

Alert encoding options:

• Encode alert - the whole alert content will be URL encoded and if necessary formatted as a parameter named text;
• Do not encode - the alert content will be sent exactly as specified with no encoding whatsoever;
• Encode tag values only - The tag values in the alert content will be URL encoded and the rest of the content will be left as defined.

Examples
Here is how a request will look like with different scenarios. Please note that some of the resulting requests below are broken and will probably be parsed incorrectly by most web servers.

We will use the following configuration to generate the requests
URL: http://alerts.domain.com/
Alert content: Target < label > down.
Target label: My target!

GET requests

- Encode alert
GET http://alerts.domain.com/?text=Target+My+Target%21+down.

- Do not encode
GET http://alerts.domain.com/?text=Target My target! down.

- Encode tag values only
GET http://alerts.domain.com/?text=Target My+Target%21 down.

POST requests

- Encode alert
POST http://alerts.domain.com/

text=Target+My+Target%21+down.

- Do not encode
POST http://alerts.domain.com/

Target My target! down.

- Encode tag values only
POST http://alerts.domain.com/

Target My+Target%21 down.

---

Similar topics

Knowledge base

• Enable HTTP Compression
  
• Accept-Language HTTP header
  
• Notification Limit Reached Alert
  
• Failures before sending an alert
  
• Protocol and Content related alerts
  

Howtos

• Configure Alert Dependencies
  
• Safely Monitor Backend Databases
  

Glossary

• ASCII / American Standard Code for Information Interchange
  
• Content Match
  
• Alert
  
• Numeric Pagers Contacts
  
• Voice call contact
  

Frequently asked questions

• Is it possible that some of the alerts I receive are false?
  
• How to monitor a SQL server?
  
• Can WebSitePulse.com notify multiple contacts upon a failure?
  
• What does it mean when my contacts are notified that my system is down?
  
• Can you monitor wireless routers?