i have rest web service issue logontoken when authenticate. subsequent rest calls require logontoken passed in header x-sap-logontoken.
i've used response body key path in paw insert logontoken retrieved in first rest call in other rest calls' headers. works fine, except 1 caveat. @ point, response body history of initial authentication call removed, depending on http exchanges in history setting.
one obvious solution (workaround?) set value of setting high, has implications on performance / resource usage of app in general, , @ 1 point, limit still reached , response body removed.
ideally, should able either set http exchange limit per request, instead of globally, or have setting keeps response body of given request being purged.
while can generate new logontoken executing initial rest call again, problem give me new session on server, , whatever actions i've taken in previous session lost (as don't know nor saved value of initial logontoken).
sorry late answer! default value of "http exchanges in history" preference 300. of latest version of paw, number isn't causing performance hit (as case in older version of paw). should safe setting again higher limit (a few hundred).
to give insight, paw stores large data blobs in external files, larger requests/responses, performance should fine.
about "response body key path", yes relies on history…so if response has been wiped out history, won't available dynamic value.
Comments
Post a Comment