Question

pxThread.pxReqExportURI vs pxProcess.pxServiceExportPath - are these properties always pointing to same location?

pxThread.pxReqExportURI vs pxProcess.pxServiceExportPath - are these properties always pointing to same location?

I have noticed that, If a file is stored in the Service Export path, we can download the same file like an URL if the file name is appended with the pxThread.pxReqExportURI. But condition is you must hit the URL in the same session when you are copying the pxReqExportURI property value from clipboard. Because it contains the session info.

Now my concern is, how pega generates the pxReqExportURI property? Are these always pointing to the same service export path of that application (pxProcess.pxServiceExportPath)?

Also let me know if any other configuration i should be aware of related to this.

Sample values:

pxProcess.pxServiceExportPath = file://web:/StaticContent/global/ServiceExport/

pxThread.pxReqExportURI = http://tomcat01.svr.company.net:8081/prweb/PRServlet/_m2FHu8Ym8Jrwb4LTqRZ4w%5B%5B*/ServiceExport

Comments

Keep up to date on this post and subscribe to comments

Pega
December 9, 2018 - 11:57am

Hi ,

seems like yes, you can have look at below discussion which might help you.

https://community1.pega.com/community/product-support/question/how-download-file-server-using-anchor-links