Passing Header properties in Rest Service Response
Hi All,
We need to set some header Parameters for Rest Service Response. It's a cloud based application with very high volume ( 2000 transactions per sec)
We were wondering what is the best option for it.
1. Set Header in Response tab of the service rule
2. Configure the Header at the Server layer
3. Any Other?
These are the headers we need to set
Access-Control-Allow-Credentials
Access-Control-Allow-Methods
Access-Control-Allow-Origin
Content-Encoding
Content-Type
Connection
P3P
Pragma
Transfer-Encoding
Thank you for you response @nkur.das.
I am also trying to find out the impact of setting these Header properties.
If we set these properties, do we need to handle the response in any different way?
Specifically the content-encoding and transfer-encoding header fields?
If we set these properties, do we need to handle the response in any different way?
Yes, you may need to. The only option to find out exactly would be to test it out using various application specific values.
We are still looking for Answers for this.
Hi agarl,
We've been trying to locate a SME to help you with this but they've asked for some more clarity from you beyond what has been commented above on your thread. How else can we help you?
Thanks so much in advance!
It depends on your requirements / need.
* If your response headers are generic, would not change across different rest services and if you would like to minimize modification / maintenance deployment of application rules to incorporate any future changes - Having the response headers set at the Webserver makes more sense.
* However, if you need fine grain control of the headers across various REST services, the headers are different across different services and if you would like to map values dynamically from the Pega clipboard then - Having the response headers in the REST service rule-form's response tab makes more sense.