Highlighted
Absent Member.
Absent Member.
689 views

Simulating File Upload through Vugen

I am Facing a challenge of Uploading a File (Can be any type) through Vugen Script . While trying to correlate , I found that there is a huge value which is coming in the Upload transaction is similar for Multiple Requests . The value (40UHVibGljJTIwRm9...) is coming in the Request Header in the generation log  and unable to correlate the value . This is Open Text Application  . I am seeking for your suggestions to fix the issue . I am pasting the particular request below 

 

web_custom_request("{Corr_JobID}",
"URL=https://urlname/otmmapi/v1/jobs/imports/{Corr_JobID}", (https://urlname/otmmapi/v1/jobs/imports/{Corr_JobID})
"Method=PUT",
"Resource=0",
"RecContentType=application/json",
"Referer=https://urlname/otmm/ux-html/index.html?p=" (https://urlname/otmm/ux-html/index.html?p=)
"folders%2F2f1294566e9b3310d8f2b2a12c4c31e2e2cc52f5%40UHVibGljJTIwRm9sZGVycyUzQyUyNiUzQiUyNi8lM0UyMDEyJTNDJTI2JTNCJTI2LyUzRVVTJTNDJTI2JTNCJTI2LyUzRU1rdF9QbGFuX1Rlc3QlM0MlMjYlM0IlMjYvJTNFQmFja1RvU2Nob29sJTNDJTI2JTNCJTI2LyUzRUZseWVyJTNDJTI2JTNCJTI2LyUzRVAyMzQ1JTNDJTI2JTNBJTI2LyUzRUFSVEVTSUEuUFVCTElDLlRSRUVOJTNDJTI2JTNCJTI2LyUzRWM3Y2E1YWZmNTgzODRjZjFhYjVmYzY5NWVjMzkxNjhhNzNkOTA1ZDYlM0MlMjYlM0IlMjYvJTNFYzMyZGI1ZTY5NGFlMmU5ZWFjMWY3NzYyMGNlMDA3OThhOTU4ZGJjYyUzQyUyNiUzQiUyNi8lM0U3MjViMzg2Y2QxNGFhMzk1NGEyO"
"DFkNzlhMmRiMTc4ODUwYzRjY2NjJTNDJTI2JTNCJTI2LyUzRTM3NzM1YzNjYzE3ZWZkZDU2NDdiMmUyODY4YWMyZTI1ZmFlMDA4NjIlM0MlMjYlM0IlMjYvJTNFYmM4MDI2ODhhYzIwMzRjYjVjNGVhMmMzNmZiOWZkYmI1NTBmMGMyYyUzQyUyNiUzQiUyNi8lM0UyZjEyOTQ1NjZlOWIzMzEwZDhmMmIyYTEyYzRjMzFlMmUyY2M1MmY1%400x100xasc_xNAME",
"Snapshot=t229.inf",
"Mode=HTTP",
"Body=-----------------------------7de3425b0584\r\nContent-Disposition: form-data; name=\"import_template_id\"\r\n\r\n{Corr_TemplateID}\r\n-----------------------------7de3425b0584\r\nContent-Disposition: form-data; name=\"parent_folder_id\"\r\n\r\n2f1294566e9b3310d8f2b2a12c4c31e2e2cc52f5\r\n-----------------------------7de3425b0584\r\nContent-Disposition: form-data; name=\"import_job_id\"\r\n\r\n{Corr_JobID}\r\n-----------------------------7de3425b0584\r\nContent-Disposition: "
"form-data; name=\"manifest\"; filename=\"blob\"\r\nContent-Type: application/json; charset=UTF-8\r\n\r\n{\"upload_manifest\":{\"master_files\":[{\"file\":{\"file_name\":\"apple.png\",\"file_type\":\"image/png\"}}]}}\r\n-----------------------------7de3425b0584\r\nContent-Disposition: form-data; name=\"file_name\"\r\n\r\napple.png\r\n-----------------------------7de3425b0584--\r\n",
LAST);

 

 

0 Likes
3 Replies
Highlighted
Absent Member.
Absent Member.

Re: Simulating File Upload through Vugen

The %40 is an url encoded character for '@'. Please try use the url dfe before correlation.

Another solution is manually correlation. Also the correlation string should include '%'.

 

Best Regards

Charlie

0 Likes
Highlighted
Regular Contributor.
Regular Contributor.

Re: Simulating File Upload through Vugen

i am facing the same issue, please let me know if u have the solution

 

0 Likes
Highlighted
Acclaimed Contributor.. Acclaimed Contributor..
Acclaimed Contributor..

Re: Simulating File Upload through Vugen

The text is a combination of URL-encoding with between '@' and '@' (the two %40 values) Base64 encoding. When you decode the Base64 section, you will find again text that is URL encoded. So it is a puzzle to find the right correlation (or it is JS generated data that matches with what you want to upload).

The text comes down to:

 

Spoiler
Public Folders
<&;&/>2012
<&;&/>US
<&;&/>Mkt_Plan_Test
<&;&/>BackToSchool
<&;&/>Flyer
<&;&/>P2345
<&:&/>ARTESIA.PUBLIC.TREEN
<&;&/>c7ca5aff58384cf1ab5fc695ec39168a73d905d6
<&;&/>c32db5e694ae2e9eac1f77620ce00798a958dbcc
<&;&/>725b386cd14aa3954a281d79a2db178850c4cccc
<&;&/>37735c3cc17efdd5647b2e2868ac2e25fae00862
<&;&/>bc802688ac2034cb5c4ea2c36fb9fdbb550f0c2c
<&;&/>2f1294566e9b3310d8f2b2a12c4c31e2e2cc52f5

 

 

Signature:
Reward community members who take time to respond and help.
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.