What is this?

This knowledgebase contains questions and answers about PRTG Network Monitor and network monitoring in general. You are invited to get involved by asking and answering questions!

Learn more

PRTG Network Monitor

Intuitive to Use. Easy to manage.
300.000 administrators have chosen PRTG to monitor their network. Find out how you can reduce cost, increase QoS and ease planning, as well.

Free Download

Top Tags


View all Tags

URL encoding

Votes:

0

Your Vote:

Up

Down

When I configure HTTP Transaction sensor to GET the URL: http://example.com/hash?files=/data/0730a418-fa84-4a4a-b7cc-6b3

It translates it t: http://example.com/hash?files%3D%2Fdata%2F0730a418-fa84-4a4a-b7cc-6b3 which my receiving part can not digest.

So it encodes the = to %3D and / to %2F.

Is it possible to disable the HTML URL encoding per sensor? If not, how can I workaround it, saying that I realy need to deliver the URL as is, without the encoding.

encoding http sensor transaction url

Created on Feb 20, 2020 2:37:35 PM by  RichardMader (0) 1



Replies

Nobody has replied yet

Why not be the first?

Please log in or register to enter your reply.


Disclaimer: The information in the Paessler Knowledge Base comes without warranty of any kind. Use at your own risk. Before applying any instructions please exercise proper system administrator housekeeping. You must make sure that a proper backup of all your data is available.