View all FAQs about Project Deployment and End-user Installation
Dynamic Web TWAIN issue in Chrome 101
Latest Update from Google:
September 27, 2022: Google has stated that the pre-flight changes will not occur sooner than Chrome version 109, which according to Google’s release calendar, is scheduled for early 2023.
July 7, 2022: Google has updated the timeline for this preflight request feature. The experiment is scheduled again for Chrome 104 and may be released in Chrome 107 at the earliest. Please refer to Google’s feature updates here.
March 7, 2022: The experiment in Chrome 98 was rolled back due to stability and compatibility issues discovered in the rollout to Chrome stable. These issues will be fixed before the experiment is tried again, no earlier than in Chrome 101. Learn more in the email@example.com Intent to Ship email thread for more details.
In Chrome 101 at the earliest, when visiting a website that has Dynamic Web TWAIN SDK v17.2 or older integrated into the application, you may see the following error message in the browser console. For the end users of your website, they may be prompted repeatedly to download and install the Dynamsoft Service.
NOTE that the same issue will also occur in any browser based on Chromium 101+, such as Microsoft Edge 101.
Access to XMLHttpRequest at 'https://local.dynamsoft.com:****' from origin 'https://yourwebsiteURL' has been blocked by CORS policy: Response to preflight request doesn't pass access control check: No 'Access-Control-Allow-Private-Network' header was present in the preflight response for this private network request targeting the `local` address space.
In Chrome 98, you may have already noticed the following warning/error message in the browser console, but it is not expected to cause any immediate issues. Per Google’s message below, Chrome 101 is expected to be released in April 2022.
A site requested a resource from a network that it could only access because of its users' privileged network position. These requests expose devices and servers to the internet, increasing the risk of a cross-site request forgery (CSRF) attack, and/or information leakage. To mitigate these risks, Chrome will require non-public subresources to opt-into being accessed with a preflight request and will start blocking them in Chrome 101 (April 2022).
As a part of the Private Network Access (PNA) specification, Chrome is deprecating direct access to private network endpoints from public websites. In Chrome 101 at the earliest, Chrome will enforce explicit permission from private network endpoints before requests from public websites can be allowed. According to Google, “this will begin only if and when compatibility data indicates that the change is safe enough and we’ve outreached directly when necessary.” More details can be found at https://developer.chrome.com/blog/private-network-access-preflight/.
Dynamic Web TWAIN utilizes a local service named ‘Dynamsoft Service’ to support document scanning from physical scanners. Your web scanning page needs to make requests to localhost or 127.0.0.1 to communicate with the local service. In Chrome 101, the connection from your public website to the private network (i.e. localhost/127.0.0.1) will be blocked.
To avoid this potential issue, you can apply one of the following solutions:
Upgrade Dynamic Web TWAIN SDK to version 17.2.1 or later
In version 17.2.1, we have made changes to handle preflight requests on our end to resolve the issue. You can test the latest version with our free trial and when you are ready to upgrade, please contact firstname.lastname@example.org to request the upgrade.
Please note that once upgraded, the Dynamosft Service on all client machines also need to be updated. You may consider installing Dynamsoft Service silently.
Disable Private Network Access checks using enterprise policies
If you have administrative control over your users, you can disable Private Network Access checks using either of the following policies:
For more details about managing policies for your users, please refer to Google’s help center article.
If you need more time to implement the solution
Register for Google’s deprecation trials to request a time extension so your website will not be affected during the trial period which will last for at least 6 months.
In this article: