Error status or error message not show when add if-none-match etag in api

iriyazuddin

when we add if-none-match header in api it should show error response or add error response or error status in api so we can use it for caching.

iriyazuddin

please reply how i can achive error status on adhan api

meezaan

I don't understand what you mean by error response. The API would not throw an error if the if-none-match header value does not match, it would, at best, return a 200.

If it matches, if will return a 304, and I can see that the Gateway does return a 304 of cached responses.

What is the query you are making and what is the problem you are having?

iriyazuddin

my concern is that the Status Code header is only shown on status 200 but not in 304 or 423
example image link:-
example image 1
example image 2

meezaan

It does not look the you actually received a response. What does your console show for the red HTTP call with provisional headers?

iriyazuddin

yes, it didn't receive a response because it matched with the ETag header but it also did not show the status code or request method.
Http Call Image

meezaan

That is the assumption you are making.

But you did not answer my question. What does your console show?

And is this a GET or an OPTIONS call?

iriyazuddin

This is a GET request and it shows a cross origin issue on the console.

meezaan

iriyazuddin please share the screenshot with the error message.

iriyazuddin

error screenshot

error message:- Access to XMLHttpRequest at 'https://api.aladhan.com/v1/calendar/2023/4?latitude=28.5473719&longitude=77.3013523&method=1&school=0&midnightMode=0&latitudeAdjustmentMethod=3' from origin 'http://192.168.236.135:8100' has been blocked by CORS policy: Request header field if-none-match is not allowed by Access-Control-Allow-Headers in preflight response.

meezaan

iriyazuddin OK, now we know what the actual problem is.

I have allowed the header, but please note at this point in time the actual API is not comparing the header value and the response to return a 304. You will only get an HTTP 304 if the response is cached in the API Gateway, if for some reason the Gateway decides the request is a cache miss or by pass, you will still get a 200.

I do want to understand why you are complicating your life by implementing this on a date based API? If the date changes, obviously the timings are different.

It would make sense for the Qur'an API, sure, so I will add this code to it.