DYMO Connect Web Service not compatible with Google's new PNA preflight request coming in Chrome v101

[Cr0aten]

It appears that the DYMO Connect Web Service is not compatible with Google's new PNA preflight request initiative (https://developer.chrome.com/blog/private-network-access-preflight/).

As such the ability to print via the DYMO Connect Framework will stop working when Chrome v101 is released in April 2022 since response headers from the DYMO Connect Web Service do not include the "Access-Control-Allow-Private-Network: true" header as required.

Are there any plans or ongoing efforts to update the DYMO Connect Web Service to be compatible with PNA preflight requests?

Thanks

!

[0xE1]

This is critical to be implemented on all platforms for both DCD on Windows and DLS on other Platforms, not just DCD, in combination with CORS issues in DCD, we may end up with DLS no longer working, and DCD yet working.

[dymosoftware]

Please try with this beta version of DCD 1.4.3. PNA header is added in this version.

[Cr0aten]

Hello,

In DCD 1.4.3.147 beta, the DYMO connect service is still not returning the "Access-Control-Allow-Private-Network: true" header for the PNA Preflight request (see attached). It looks like the service is returning the header for the actual resource request, but not for the Preflight request as required by PNA.

[dymosoftware]

Hello,

In DCD 1.4.3.147 beta, the DYMO connect service is still not returning the "Access-Control-Allow-Private-Network: true" header for the PNA Preflight request (see attached). It looks like the service is returning the header for the actual resource request, but not for the Preflight request as required by PNA.

Could you try with this new beta version 150?

[Cr0aten]

The DYMO connect service is still not returning the "Access-Control-Allow-Private-Network: true" header for the PNA Preflight request in 1.4.3.150 beta

[BillDuggin]

As of Chrome 98 (on Mac) this issue completely freezes Javascript on any page that tries to use the DYMO Connect Web Service. The user must select "Stop Service" in the Dymo web connect menu in order to un-freeze the page.

We are eagerly awaiting a fix from Dymo.

[0xE1]

Using DYMO init and checkEnvironment functions in async prevents page from freezing, but doesn't solve anything else.

[Cr0aten]

Any updates on this? We're about a month out from Google releasing Chrome v101 and breaking compatibility with DYMO connect framework.

[Cr0aten]

Google has now changed the implementation timeline for this to roll out in Chrome v105 in Aug 2022. Any updates on compatibility updates with the DYMO connect framework? As it stands right now, DYMO printing functionality via the DYMO connect framework will no longer work once this update gets implemented in Chrome v105.

[Cr0aten]

Looks like Google has changed the timeline once again. Google has now changed the implementation timeline for this to roll out in Chrome v107 in Oct 2022. Any updates on compatibility updates with the DYMO connect framework? As it stands right now, DYMO printing functionality via the DYMO connect framework will no longer work once this update gets implemented in Chrome v107.

[ghost]

@dymosoftware Any update on this?

[Cr0aten]

Looks like Google has changed the timeline once again. Google has now changed the implementation timeline for this to roll out in Chrome v113 in Apr 2023. @dymosoftware Any updates on compatibility updates with the DYMO connect framework? As it stands right now, DYMO printing functionality via the DYMO connect framework will no longer work once this update gets implemented in Chrome v113.

[Cr0aten]

It looks like the "Access-Control-Allow-Private-Network: true" header has been added to the pre-flight request in the latest beta of the Dymo Connect web service...Which I am ABSOLUTELY THRILLED to see!!!

However, it looks like the "Access-Control-Allow-Origin: *" header (which used to be included) has now been removed from the pre-flight request, so the browser is now generating a different error.