Question
Skillstorm
US
Last activity: 22 Jan 2025 21:02 EST
multipart/form-data service responds with the wrong attachment type
I have a service in pega which responds with multipart/form-data content. In my activity I have an example set up where it should send a simple text file.
Then I run the command
wget --user <<myusername>> --password <<mypassword>> <<enpointURL>>/events
And a new file called "events" is created and inside it has
--z8pxifJXtO3KqznAW_UPYELrk820ilJXa58MyE
Content-Disposition: form-data; name="events"; filename="events"
Content-Type: application/octet-stream; charset=ISO-8859-1
Content-Transfer-Encoding: binary
Here are some events
--z8pxifJXtO3KqznAW_UPYELrk820ilJXa58MyE--
How can i make it just download the events.txt file instead of this event file that is of type application/octet-stream?
HCA Healthcare
US
@IlyaK17181477 To resolve the issue, configure your Pega activity to set the correct headers for the response. Use the Property-Set method in the activity to set pyHTTPResponseHeader with Content-Type: text/plain and Content-Disposition: attachment; filename="events.txt". Ensure the file content (e.g., "Here are some events") is placed in pxRequestor.pyResponseBody. In the Service REST rule, go to the Response tab and set the Media Type to text/plain. When you test with wget, these headers will ensure the file is downloaded as "events.txt" instead of a generic file, and the content will be correct. Use tools like Postman or curl to verify that the response headers and body match your expectations. If configured properly, the file should download with the right name and type.
Skillstorm
US
@Sairohith Thank you, but I am not sure I set it up properly
I added a Requestor page from Code-Pega-Requestor in Pages and Classes in my activity
Then I added a Property-Set step in my activity which sets the .pyHTTPResponseHeaders property in the Requestor page to "Content-Type: text/plain, Content-Disposition: attachment, filename=\"events.txt\""
But I am still receiving the same output when I hit the endpoint. What part of my setup was done incorrectly?
HCA Healthcare
US
@IlyaK17181477 To fix the issue, ensure the pyHTTPResponseHeader is set correctly in your Pega activity. In the Property-Set step, set the .pyHTTPResponseHeaders property as a single string with headers separated by \r\n, like this: Content-Type: text/plain\r\nContent-Disposition: attachment; filename="events.txt". Use the existing pxRequestor page instead of adding a new one. Also, ensure the response content, such as "Here are some events," is set in pxRequestor.pyResponseBody. In the Service REST rule, verify that the Response tab does not conflict with these headers and that the Media Type is set to text/plain. If configured correctly, the response will include the proper headers, and the file will download as events.txt with the expected content. Test the endpoint using tools like Postman or curl to confirm the headers and content are correct. If the issue persists, check for other logic in the Service REST rule that might override the headers. Please let me know if you still face any challenges. Thanks
Skillstorm
US
@Sairohith There doesn't seem to be a pxRequestor page in the activity that I can use, how can I access this page?
HCA Healthcare
US
@IlyaK17181477 The pxRequestor page is automatically created by Pega during the execution of a service, so you don’t need to add it manually. In your activity, you can directly use the pxRequestor page to set properties like .pyHTTPResponseHeaders and .pyResponseBody. For example, in a Property-Set step, set pxRequestor.pyHTTPResponseHeaders to Content-Type: text/plain\r\nContent-Disposition: attachment; filename="events.txt" and pxRequestor.pyResponseBody to the content, like "Here are some events." Ensure your activity is triggered by the service, as the pxRequestor page is only available in the context of a running service. If you're unsure, use a Log-Message step to verify if the pxRequestor page exists during runtime. Make sure the Service REST rule is correctly configured to call this activity and does not override your headers. When done, the service should respond with the correct file and headers. Thanks