Recent update of chrome 80 forced us to update tomcat 8.5 for samesite=none in context.xml file.
Our web application is working intermittently in an iFrame section of clients web application.
Even latest safari browser version 13.1 throws session expired issue because of jsessionid cookie is not set properly.
Is there any specific fix has been implemented ?
Related
I am using Identity Server 4 (4.1.2) in my .Net core app. My client app is developed using .Net framework 4.6.1. I implemented authentication using identity server 4 and it is all working fine locally in both firefox and chrome.
After I deployed code to server, when I try to login to application, I am getting blank screen after I click on login in chrome. I can see, it is generating token correctly but while redirecting it is showing blank screen. I can see cookie is not set properly in chrome. I don't see any console errors in chrome dev tools.
When I tried same in firefox, it is working fine without any issues.
Am I missing any specific setting for cookies in chrome? Any help would be really useful.
We build a website in asp.net and it was working fine. Last 2-3 days I noticed it took lots of time (more than 30 sec) to load the page only on Chrome and Mozilla. Other browsers (Safari, Internet Explorer etc) are working fine.
I'm using Chrome latest version 74.0.3729.131 (Official Build) (64-bit). In the developer's console, it shows the following error message for each request
Then I noticed those requests are timeout because of HTTPS. I request the page with HTTP then it's loading fine. But my website is HTTPS so I should request all with HTTPS unless it don't load the page.
example - https://ajax.aspnetcdn.com/ajax/4.5.1/1/WebForms.js
I also tried the following ways but it couldn't work,
Uninstall and reinstall Chrome.
Delete all cookies and sessions.
Restarted wifi router (IP changed).
Restarted firewall.
But it works on some of the client machines and when I use chrome proxy extension and visit the website from a different country. I feel the issue is from the network or IP address. I don't know how to fix it. Please help me to fix...
I'm running a Spring Boot application with an Angular 6 front end, on a Windows 8 server with IIS 8.5 set up as the reverse proxy (redirecting the site URL to localhost:8090) Originally I had a problem where all the PUT requests from the front end return 403, but only with Chrome and Safari, not Firefox. GET and POST requests are fine.
I am not an expert on setting up IIS, or proxy servers, by my guess is that this was because IIS was stripping out the headers that allowed CORS requests, and possibly other headers as well.
This original problem I fixed on the unsecure site, with the help of this SE: Modifying headers with IIS7 Application Request Routing
However, now the same thing is happening on the HTTPS secure site, and I don't understand what setting I should change to make this work as well.
I would also like to better understand the reason why this is failing on the secure site but not the unsecure site, and also why it fails on Chrome but not Firefox.
I am writing a web application that is meant to me utilized "sometimes" offline using the iPad's home bookmarked feature of Safari . By "sometimes", I mean that the app should work if the iPad is offline and data has been cached. If the iPad is online and the cache manifest has changed, the app should update the contents of the cache. The web page is protected through https.
Currently, I can get my app to work correctly using Chrome, Firefox, and Safari. I have tested them all in windows 7 and windows XP. The app also works correctly in the iPad's "normal" way of using Safari, but when I run the bookmarked version of the app (created by specifying the special standalone apple metas and then bookmarking) it does the initial password prompt and correctly moves on to download all the data specified in the cache manifest file. The trouble is that any subsequent runs of the standalone app do not seem to have access to the manifest file and thus any later updates to the manifest file do not get reflected.
So my question is this: does HTML5 specific caching work on the iPad (ios6) with https on a stand alone (bookmarked) web app?
Application Caching on iPad will not cache website data or pages
I was having the same problem. This answer worked. Hope it does for you too!
I have a HTML5 webapp which is running perfectly when served via the IIS without authentication.
Is is using a cache.manifest file.
Both when running in safari, and as an "add to homescreen" fullscreen app, once I update the manifest file on the server, and the app will update.
When I turn on authentication on all files except the cache.manifest, then I only see the update when running it in the safari browser.
If I add it to the homescreen, I am not able to make the app update the cache.
If I wireshark the traffic on the server, I can see the manifest file is fetched without problems, but all the files in the manifest file hits a 401 Unautorized error.
Any idea how I can fix this? Running it in the safari browser is working..
Any help is highly appreciated.
Safari is much more aware of HTTP Basic Auth, but web.app (the home screen web app handler, which is basically a UIWebView wrapper) isn't as full-featured and doesn't appear to support basic auth.
It seems you may need to work around this with either a server-side solution to append an authentication key to the filename (such as application.css?longhexkey) to bypass basic auth, or go with a more traditional login form (which may require significant changes to your app)
Same issue on Sencha forums: Unanswered: Forcing re-authentication after offline usage on iOS devices?