We've Moved! Please visit our new and improved forum over at our new portal: https://portal.plumvoice.com/hc/en-us/community/topics

<data> - Prevent input string display in log

Questions and answers about IVR programming for Plum DEV

Moderators: admin, support

Post Reply
vikas
Posts: 53
Joined: Wed May 13, 2015 7:46 pm

<data> - Prevent input string display in log

Post by vikas »

We are facing a problem with <data> tag. We use <data> tag to invoke backend API to fetch data.

The <data> request uses GET. When a GET request is made the entire URL with query string is shown in the logs like this:

https://kyslegacy.blackhawknetwork.com/ ... ation=xxxx[/b]

How can we prevent <data> request to display query string?
Since the query string contains sensitive customer information we don't want it to be shown in log.

support
Posts: 3632
Joined: Mon Jun 02, 2003 3:47 pm
Location: Boston, MA
Contact:

Re: <data> - Prevent input string display in log

Post by support »

Hi,

Please note that you should always mask credit card data in your forum posts. We went ahead and replaced the info in your post with x's, but please be cautious about posting sensitive data on our support forums.

In order for query variables to not show up in your call logs, you can either use the logging property to disable logging for that area of your script like such:

Code: Select all

<property name="logging" value="disable"/>
{insert code you do not want to show up in the call logs here}
<property name="logging" value="enable"/>
Alternatively, you should use POST instead of GET to avoid query parameters showing up in the call logs.

Code: Select all

<data name="result" src="example.com" namelist="some_data" method="post"/>
Using this sample, you would see the request url as example.com in your call logs.

Please let us know if you have any questions.

Regards,
Plum Support

vikas
Posts: 53
Joined: Wed May 13, 2015 7:46 pm

Re: <data> - Prevent input string display in log

Post by vikas »

Thanks. However I have one more question.

Taking below error log as an example.
"_event" variable would print "error.badfetch.http.405".

Is there some other variable that will display the entire error string i.e. "HTTP/1.1 405 Method Not Allowed - https://plumvoicepp.blackhawk-net.com:4 ... ntservices.......................................

I will be setting logging to disable. Therefore need to store the entire error message for logging later.
====================================================================================================
Attempting to fetch https://plumvoicepp.blackhawk-net.com:4 ... ard/status


Mon 01 Jun 2015 06:25:51 PM EDT:

HTTP/1.1 405 Method Not Allowed - https://plumvoicepp.blackhawk-net.com:4 ... ard/status
VXI::FetchXML - could not open URL: https://plumvoicepp.blackhawk-net.com:4 ... ard/status
errno: 203 uri https://plumvoicepp.blackhawk-net.com:4 ... ard/status

received event: error.badfetch.http.405:

vikas
Posts: 53
Joined: Wed May 13, 2015 7:46 pm

Re: <data> - Prevent input string display in log

Post by vikas »

I found same problem that was posted in past by someone. Link pasted below.
However I see that no solution was found.

I am also interested to store the error message generated by IVR platform.

http://support.plumvoice.com/viewtopic. ... sage#p3705

support
Posts: 3632
Joined: Mon Jun 02, 2003 3:47 pm
Location: Boston, MA
Contact:

Re: <data> - Prevent input string display in log

Post by support »

Hi,

The actual error message that you see in the call logs and error logs when an error occurs is a platform-specific error and does not percolate up to the vxml. Therefore, the best way to handle this scenario would be to log the _event with the timestamp and session id of the call, which is available in the session variables for all calls. Details here:

http://www.plumvoice.com/docs/dev/voice ... essionvars

You could then view the error logs to look up the full error based on the timestamp and session id. There is a future feature request to include an error log api to lookup errors, but the timetable on this implementation, at this time, is unavailable.

Please let us know if you have any questions.

Regards,
Plum Support

Post Reply