Added cache control to fix bug with internet explorer not updating UF table data#884
Closed
aminazirani wants to merge 1 commit intouserfrosting:masterfrom
Closed
Added cache control to fix bug with internet explorer not updating UF table data#884aminazirani wants to merge 1 commit intouserfrosting:masterfrom
aminazirani wants to merge 1 commit intouserfrosting:masterfrom
Conversation
Member
|
|
Member
|
This has been superseeded by #922 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I was using UserFrosting to implement a software solution for a client of mine and it turned out that they were Internet Explorer fans. This was when I realized that UF tables did not work well in IE 11 and possibly Edge.
After debugging for some time, I came to the conclusion that this was because of the cache headers. I believe it is generally a good idea to set cache headers to disabled for API requests that would update frequently. So I set the cache headers for all Sprunje (Json) functions to "no-cache".
This fixed the IE problem which was a significant compatibility issue for UserFrosting.