You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@monica-ch
when i am using to cache rest api response using /api/ endpoint caching is not working correctly,
when i send first request to server it send me back reponse status 200 and content with etag hash,
but when i send second request it does not reach to server due to cache, and it shows its cached and reponse 200 , you can see into below image
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
Laravel
Operating System
Fedora
OS Version
Fedora Linux 39 (Workstation Edition)
Repro steps
.
Repros in Edge Browser
I tried with chrome and edge and mozila
Regression
Don't know
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered:
Hi @rehman20281, this is the Edge WebView2 repository, and it seems like you are reporting an issue with the Edge Browser? If so, please use the following feature to report the issue
What happened?
@monica-ch
when i am using to cache rest api response using /api/ endpoint caching is not working correctly,
when i send first request to server it send me back reponse status 200 and content with etag hash,
but when i send second request it does not reach to server due to cache, and it shows its cached and reponse 200 , you can see into below image
Importance
Important. My app's user experience is significantly compromised.
Runtime Channel
Stable release (WebView2 Runtime)
Runtime Version
No response
SDK Version
No response
Framework
Laravel
Operating System
Fedora
OS Version
Fedora Linux 39 (Workstation Edition)
Repro steps
.
Repros in Edge Browser
I tried with chrome and edge and mozila
Regression
Don't know
Last working version (if regression)
No response
The text was updated successfully, but these errors were encountered: