Hi.
The customer who is using our HCP asked me the following question.
Our customer requires caching features such as 'HCP Response Header/Access-Contorl-Max-Age' to process specific/same images stored in HCP more quickly and with less I/O from 'Container-based Web Server' as shown in the configuration diagram below.
However, if you look at the 'Standard HTTP response header for the REST API' in Hitachi Vantara's 'HCP REST API reference', the value of the 'Cache-Control' header in the HCP is fixed as 'no-cache/no-store/must-validate'.
Can HCP adjust/change the life cycle of the received resource according to the Cache-Control header included in the HTTP response like AWS?
According to Hitachi Vantara's 'Using CORS to process cross-domain requests' document, it seems that you can set the response headers (Preflight request) to Strict-Transport-Security: max-age=31536000; includeSubDomains.
If I do 'Rule Setting', can the web server (browser) continue to use the cached image without requesting download to HCP until the expiration date of the image once received from HCP in container-based web server?
If anyone knows how to solve the above customer requirements in HCP, please reply.
Best Regards
Yun Myoung Han
------------------------------
Myoung han Yun
Systems Engineer
LG Hitachi Ltd.
------------------------------