Issue & Reproduction Steps

This PR implements ETag caching for all GET and HEAD requests, enhancing performance and reducing bandwidth usage by leveraging HTTP conditional requests. The middleware is now applied globally, ensuring consistent ETag handling across endpoints.

Solution

1. Global ETag Middleware:

• Applied the ETag middleware to all GET API requests to ensure consistency and avoid redundant implementation for individual routes.
• Middleware calculates and validates ETags based on the response or a configurable sources of truth (optional).

2. Exclude active_at Field:

• Removed the active_at field from TaskResource and requestor serialization to prevent ETag inconsistencies.

3. Introduce Configurable ETag Source:

• updated_at: Default method using database timestamps to determine the latest update for relevant tables.

How to Test

1. Call any GET endpoint for the first time. A 200 OK response is returned and the content is fetched from the server and cached.
2. Refresh the page or call the endpoint again. A 304 Not Modified response is returned if the ETag matches.
3. Modify the relevant data (e.g., update the database). On subsequent requests:
   • If using updated_at as the source, a 200 OK response is returned with the updated content.
4. Validate that the updated content is cached and subsequent requests return 304 Not Modified.

Related Tickets & Packages

• FOUR-20944
• FOUR-20939

Code Review Checklist

• I have pulled this code locally and tested it on my instance, along with any associated packages.
• This code adheres to ProcessMaker Coding Guidelines.
• This code includes a unit test or an E2E test that tests its functionality, or is covered by an existing test.
• This solution fixes the bug reported in the original ticket.
• This solution does not alter the expected output of a component in a way that would break existing Processes.
• This solution does not implement any breaking changes that would invalidate documentation or cause existing Processes to fail.
• This solution has been tested with enterprise packages that rely on its functionality and does not introduce bugs in those packages.
• This code does not duplicate functionality that already exists in the framework or in ProcessMaker.
• This ticket conforms to the PRD associated with this part of ProcessMaker.