Persistent OneDrive File Handler Cache After Removal
I’m a developer supporting an Azure AD application that was previously registered with a File Handler for PDF files (used to display the "Open with Lumin PDF" option in OneDrive’s context menu). The File Handler configuration was removed on June 19, 2024. However, some of our customers are still seeing the "Open with Lumin PDF" option in their OneDrive UI. This is causing confusion and additional support overhead on our side. I understand this is likely a caching issue, so I’ve asked our customers to: Clear the server-side cache by following https://learn.microsoft.com/en-us/onedrive/developer/file-handlers/reset-cache?view=odsp-graph-online Clear their browser cache, re sign-in in a new browser profile I’ve already tried all possible solutions within my control to resolve this caching issue, but none have been effective. What else can I do to address this?
Disabling Certificate Revocation List (CRL) Caching on IIS 10.0
Background Hello, community members! I am trying to disable CRL caching on IIS 10.0 in order to be able to fetch updated version of CRL each time I make a request to my website. It is required for development purposes: I revoke or un-revoke client certificate, publish latest CRL on my CA and want IIS to check the latest information. Setup What I completed as a setup step: Exported root CA certificate and installed it on my computer by following these articles: https://learn.microsoft.com/en-us/troubleshoot/developer/webapps/iis/health-diagnostic-performance/http-403-forbidden-access-website and https://learn.microsoft.com/en-us/troubleshoot/windows-server/identity/export-root-certification-authority-certificate. Set "Accept" for client certificates on IIS. Checked following materials about IIS CRL settings: CRL checking by IIS - Microsoft Community Hub, https://learn.microsoft.com/en-us/windows/win32/api/http/ns-http-http_service_config_ssl_param, https://learn.microsoft.com/en-us/archive/blogs/kaushal/disable-client-certificate-revocation-crl-check-on-iis. Actions What I am trying to do to disable CRL caching on IIS: Delete existing SSL binding for my website: netsh http delete sslcert ipport=0.0.0.0:3010. Add binding which tells IIS to download CRL each 10 seconds and not to cache it (see bold text): netsh http add sslcert ipport=0.0.0.0:3010 certhash=SOME_VALUE appid={SOME_VALUE} certstorename=My verifyclientcertrevocation=enable revocationfreshnesstime=10 urlretrievaltimeout=30000. Bold text parameters mean that we enable CRL checking, refresh CRL each 10 seconds and set HTTP timeout for CRL download to 30 seconds (30000 milliseconds). Verify that the information has been updated. If CertCheckMode is set to 4, certificate revocation verification will be done by downloading the remote CRL, even if we have the valid cached CRL on the server. It ignores the cached CRL completely. Restart IIS or reboot the machine: iisreset. Clear CRL cache: certutil -urlcache crl delete. Publish new CRL and verify that it doesn't contain our certificate. Send not revoked certificate: 403 status has been returned by IIS. This means that IIS uses cached CRL and above-mentioned settings for IIS doesn't work. If I disable CRL checking it works: verifyclientcertrevocation=disable. CRL is reachable. Question What settings should I change in order to disable CRL caching on IIS 10.0? I want IIS to download CRL each time I make a request to it.[O365] Global Hub site navigation and communication site titles cached even after weeks...
Even weeks after changes have been made to the global structured navigation on our hub sites or to site titles on communication sites belonging to a hub site, some users keep seeing the old navigation or standard "communication site" title. Switching to a different browser, clearing cookies or using in private mode does not resolve this. This is only happening to some users, and there is no common ground to be found. Are we the only onces experiencing this? Does any one have a clue on how to fix this?
Redis - suddenly stops responding
Hi there, We are running a setup consisting: - S3 web app in UK South - S2 failover in UK West - 200DTU Elastic Pool with around 25 databases - Redis server Several times this week, we have had periods where Redis has stopped hitting and missing data, and no additional items are being added to the cache. In effect the caching completely ceases being available. Flushing the cache does not make any difference to the issue - nothing is added, nothing is hit or even missed. The only way to re-enable is to restart the web app itself. After which everything is back to normal. I have attached an example showing gaps between around 11am-1pm where cache suddenly stopped functioning, and the effect of a restart can be seen. Our developers are looking into potential causes in our codebase, but I wonder if anyone has any ideas on how to diagnose or solve this issue. Thanks
