In case you've encountered any issues while browsing/reviewing website proofs, please refer to the instructions below:
Why is my live website proof not loading correctly in the viewer?
The Ziflow proof viewer is hosted securely (HTTPS). To support "non-secure" sites (HTTP), we load them using our own proxy servers since the browsers don't allow mixed content (secure and non-secure) to be loaded at the same time.
If the non-secure site contains any direct links to other non-secure content, the browser will load this directly and it will not be proxied via our servers. In this case, the browser will block the content and your site may not load correctly.
There are two ways to fix this:
Host the website securely (HTTPS).
Change links in the web page from absolute to relative paths. You can either do this by editing your original website or you can let Ziflow attempt to do this automatically when loading the website:
Go to Manage Account > Proofing Settings > Proof Viewer > Other options and activate Live websites: URL rewriting
You can also try disabling the proxy setting (Settings -> Proofing Settings -> Proof Viewer - > Other options) in your account and then submitting the proof once again. This might help in some situations since our proxy mechanism may not work with some types of websites.
Viewing live webpages/Rich Media files with iframe embedded:
Due to our security policy, we don't allow viewing live websites and/or rich media files which include an iframe with the following attributes:
allow-modals
allow-orientation-lock
allow-pointer-lock
allow-popups
allow-popups-to-escape-sandbox
allow-presentation
allow-same-origin
allow-top-navigation
allow-top-navigation-by-user-activation
Proofing pages protected with reCaptcha
If you want to proof the page which is protected with reCaptcha please:
Open the Settings of your v3 API Account
At the Domains option, only put in proof-proxy.ziflow.net domain
Why Ziflow Users Should Prioritize HTTPS for Proofing Sites
If you encounter issues when accessing or viewing proofing sites over HTTP, consider switching to HTTPS for a more secure and stable experience. HTTPS is now the industry standard for safe communication on the web, offering several critical benefits for proofing workflows in Ziflow.
Understanding HTTP and HTTPS
HTTP (HyperText Transfer Protocol) is the basic protocol for online communication but does not include data encryption. Without encryption, information shared between your browser and the proofing site is unprotected, making it vulnerable to interception or tampering.
HTTPS (HyperText Transfer Protocol Secure) is a secure extension of HTTP that employs encryption (TLS/SSL) to protect communication between your browser and the proofing site. This ensures that all data exchanged remains private and resistant to unauthorized access or modification.
Benefits of Using HTTPS for Proofing Workflows
Enhanced Security: HTTPS encrypts information transmitted between users and proofing sites, safeguarding sensitive data—such as user credentials, confidential proofs, and feedback—against interception.
Data Integrity: HTTPS prevents data from being tampered with during transfer, ensuring that what you view is accurate and unaltered. This is crucial for proofs, where any unintended changes can impact reviews and approvals.
User Privacy: With HTTPS, Ziflow users and reviewers can be assured that their browsing activities and feedback are protected from third parties.
Browser and SEO Compatibility: Major web browsers flag or restrict access to HTTP-only sites due to security risks, and search engines prefer HTTPS sites in rankings. Ensuring proofing links use HTTPS provides a seamless experience across devices.
HTTPS as the Standard for Security and Trust
Given the importance of data security, HTTPS has become the default standard for websites. Many browsers now require HTTPS for specific features and may block HTTP-only sites. Switching to HTTPS for proofing ensures a secure, trusted, and reliable review experience for you and your collaborators.
If you encounter access issues with HTTP-only proofing sites, check for an HTTPS version. Using HTTPS can significantly improve security and help ensure an optimal proofing workflow within Ziflow.
Supporting material: