Cache your CORS

Re:Cache your CORS by giancarlostoro on Tuesday September 20, 2022 @08:36AM (#32910818)

I feel like this is overkill when you have something like OPTIONS which is very minimalist in its response. Unless I'm missing some obvious drawback with calling OPTIONS?

[ Parent | on HN ]

Re:Cache your CORS by javier2 on Tuesday September 20, 2022 @02:35PM (#32915966)

Well, you double the latency for every. single. request.

[ Parent | on HN ]

Re:Cache your CORS by tomjakubowski on Tuesday September 20, 2022 @05:47PM (#32918235)

CORS does not double latency for every single request. It adds the additional overhead of a separate OPTIONS request for every single request. Unless the responses are as trivial to compute/serve as OPTIONS responses are, that will be way less than a doubling in latency.

[ Parent | on HN ]

Re:Cache your CORS by javier2 on Thursday September 22, 2022 @02:39PM (#32942904)

What I mean by latency is the transport latency, even assuming 0ms OPTIONS compute time, you still need twice the round trip time.

[ Parent | on HN ]