![]()
changing chrome's "disable cache" checkbox doesn't seem to effect things.the response headers include etag, gzip, content-type, date, last-modified, server, status (200), strict-transport-security:max-age=604800.the cpu / ram never get anywhere close to maxxing out when there is load on the server.Nginx version 1.9.3 # some variables we've tweaked server is run https, wildcard cert ( *. ).frontend is angularjs, accessed via chrome other browsers don't seem to have this issue. #Safari or chrome do not load network login page full#
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |