Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

SPIKE: Investigate and define latest cache-enabled OKAPI migration steps

CSP Rejection Details

None

CSP Request Details

None

CSP Approved

None

Description

It is required to clarify the following questions:

  1. Does new OKAPI support per-request cache disable option that can be switched ON via HTTP header.

  2. Does stripes-connect manifest config support custom HTTP headers and if yes then how to pass it and in which config section.

  3. If OKAPI cache is not configurable in request itself then we should find out how can we switch cache off at all.

Then if Points 1 and 2 is true we should review all our manifest configs in all the UI modules to define which of them require cache to be switched off and disable it for those requests.

In case it's helpful: Here is a file change in git: https://github.com/folio-org/okapi/pull/879/files, plus see attached notes

Environment

None

Potential Workaround

None

Attachments

1
  • 29 Jan 2020, 03:16 PM

Checklist

hide

TestRail: Results

Activity

Show:

Ann-Marie Breaux February 13, 2020 at 10:09 AM

Hi and - Mark Veksler confirmed that there is enough investigation of the okapi caching, and nothing further is needed now. He asked that I close this issue as not needed. If needed in the future, we'll open a new issue. Thank you!

Won't Do

Details

Assignee

Reporter

Labels

Priority

Story Points

Development Team

Folijet

Parent

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created January 28, 2020 at 2:36 PM
Updated November 8, 2021 at 2:16 PM
Resolved February 13, 2020 at 10:09 AM
TestRail: Cases
TestRail: Runs