Hi, I'm not sure I understand the question, but yes, having the 'ACCESS-ORIGIN' portion of the header in the http response from the printer should solve most of the CORS issue. We have not updated the firmware to solve this for several reasons. The priority has been more focused on providing connectivity through other methods that serve the greater market and are more secure.
1, I think It may be simple to update firmware with header 'ACCESS-ORIGIN'. If consider secure, can let let users to set whether add the header to it.
2, If it is solved, SAAS based on web will be well-supported. As SAAS is on internet, while usually the printer in office.
My project for example, we choose GT 820/GT 800/gk888.
BY THE WAY, I have looked into Browser Print . It does not support GT 820/GT 800/gk888.
BTW, I think browser print is not good idea. If the cors and https solved, we can scan printers via http. and it's better to add zebra information to header.