Quantcast
Channel: LivePerson Connect : Popular Discussions - All Communities
Viewing all articles
Browse latest Browse all 2324

Ticket Export

$
0
0

A few months ago, we build a VB.net application that would collect chat history in xml format and parse this file to add to our company database which is then used for business analysis purposes. We use the class HTTPWebRequest to create a connection string which passes our site, username and password information along with a startDate and endDate which kicks off a LivePerson search engine request to assemble the correct information. This application is then assigned as a sceduled task that run automatically each day at 3:00 am and has been running successfully without issue.

 

The problem: I'm creating an almost exact duplicate of this application that that is designed to download Ticket Export (email) information. I can manually create a connection string with the proper parameter set and paste this into a browser window and the download process cycles to create the report.xml file. However, when I attempt to run this connection string using the HTTPWebRequest function, I'm redirected to a login page which indicates an incorrect user or password value, yet these values to the LivePerson server have been confirmed as correct and is exactly the same as when I do so manually.

 

Has anyone run into this issue?

Because the Ticket Export is validated through a ticketExport.jsp (java server page), I'm curious if any special HTTPWebRequest settings/ values are required. I've attempted to offset some values such as .KeepAlive = false and .ProtocolVersion= HttpVersion.Version10. Yet the key issue is validating the user/password combination though code. Instead of downloading the report.xml file, I continue to collect the contents of the actual LivePerson html redirect page.

 

Any help, thoughts or suggestions would be sincerely appreciate!


Viewing all articles
Browse latest Browse all 2324

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>