KB-1583 Web Content Component not rendering content

Rebecca Jonas — Thu, 18 Jun 2020 20:07:48 GMT

Current Revision posted to Appian Knowledge Base by Rebecca Jonas on 6/18/2020 8:07:48 PM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The a!webContentField() is blank instead of rendering the expected page.

There is a pink box error rendering the a!webContentField():

Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content components are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP restrictions or VPN.
The pink box error is caused by using an insecure source that is served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from using a!webContentField() to embed content served over HTTP.

Action

If a web content component shows up as blank, check that:

A web browser can load the resource as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either an IP allow list or a VPN tunnel.
The source of the web content component does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

Content that uses a restrictive X-Frame-Options header cannot be embedded without changing the web server configurations of the source server. Please contact the owner of the source server to determine if this can be changed to allow embedding in Appian.

If a web content component errors out with the insecure source error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: June 2020

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-1583 Web Content Component not rendering content

Nick Vigilante — Mon, 21 May 2018 13:55:00 GMT

Revision 12 posted to Appian Knowledge Base by Nick Vigilante on 5/21/2018 1:55:00 PM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The a!webContentField() is blank instead of rendering the expected page.

There is a pink box error rendering the a!webContentField():

Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content components are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.
The pink box error is caused by using an insecure source that is served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from using a!webContentField() to embed content served over HTTP.

Action

If a web content component shows up as blank, check that:

A web browser can load the resource as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content component does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

If a web content component errors out with the insecure source error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-1583 Web Content Component not rendering content

Nick Vigilante — Mon, 21 May 2018 09:55:00 GMT

Revision 11 posted to Appian Knowledge Base by Nick Vigilante on 5/21/2018 9:55:00 AM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The a!webContentField() is blank instead of rendering the expected page.

There is a pink box error rendering the a!webContentField():

Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content components are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.
The pink box error is caused by using an insecure source that is served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from using a!webContentField() to embed content served over HTTP.

Action

If a web content component shows up as blank, check that:

A web browser can load the resource as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content component does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

If a web content component errors out with the insecure source error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-XXXX Web Content Component not rendering content

Jussi Lundstedt — Wed, 16 May 2018 10:36:25 GMT

Revision 10 posted to Appian Knowledge Base by Jussi Lundstedt on 5/16/2018 10:36:25 AM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The a!webContentField() is blank instead of rendering the expected page.

There is a pink box error rendering the a!webContentField():

Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content components are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.
The pink box error is caused by using an insecure source that is served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from using a!webContentField() to embed content served over HTTP.

Action

If a web content component shows up as blank, check that:

A web browser can load the resource as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content component does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

If a web content component errors out with the insecure source error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-XXXX Web Content Component not rendering content

Jussi Lundstedt — Wed, 16 May 2018 10:33:03 GMT

Revision 9 posted to Appian Knowledge Base by Jussi Lundstedt on 5/16/2018 10:33:03 AM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The a!webContentField() is blank instead of rendering the expected page.

There is a pink box error rendering the a!webContentField():

Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content components are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.
The pink box error is caused by using an insecure source that is served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from using a!webContentField() to embed content served over HTTP.

Action

If a web content component shows up as blank, check that:

A web browser can load the resource as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-XXXX Web Content Component not rendering content

Jussi Lundstedt — Wed, 16 May 2018 10:32:32 GMT

Revision 8 posted to Appian Knowledge Base by Jussi Lundstedt on 5/16/2018 10:32:32 AM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The a!webContentField() is blank instead of rendering the expected page.

There is a pink box error rendering the a!webContentField():

Could not display interface. Please check definition and inputs.

Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content components are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.
The pink box error is caused by using an insecure source that is served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from using a!webContentField() to embed content served over HTTP.

Action

If a web content component shows up as blank, check that:

A web browser can load the resource as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-XXXX Web Content Component not rendering content

Jussi Lundstedt — Wed, 16 May 2018 10:09:35 GMT

Revision 7 posted to Appian Knowledge Base by Jussi Lundstedt on 5/16/2018 10:09:35 AM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The web content field is blank instead of rendering the expected page.
The web content field displays a pink box error: Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content fields are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.
The pink box error is caused by attempting to embed insecure content served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content in a secure Appian environment and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from embedding content served over HTTP.

Action

If a web content field shows up as blank, check that:

The web resource is accessible as expected through a web browser.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

Content that uses a restrictive X-Frame-Options header cannot be embedded without changing the web server configurations of the source server. Please contact the owner of the source server to determine if this can be changed to allow embedding in Appian.

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-XXXX Web Content Component not rendering content

Jussi Lundstedt — Wed, 16 May 2018 10:07:32 GMT

Revision 6 posted to Appian Knowledge Base by Jussi Lundstedt on 5/16/2018 10:07:32 AM

Symptoms

When embedding content into a Web Content Component, it fails to render in one of two ways.

The web content field is blank instead of rendering the expected page.

The web content field displays a pink box error:

Could not display interface. Please check definition and inputs.
Interface Definition: Expression evaluation error at function a!webContentField[<line number>]: A web content field [label=<label>] has an invalid value for "source". Source must be secure (HTTPS). Received: http://<URL>

Cause

Blank web content fields are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.
The pink box error is caused by attempting to embed insecure content served over HTTP rather than HTTPS. In order to minimize vulnerabilities arising from embedding insecure content in a secure Appian environment and to prevent browser errors arising from serving mixed content, Appian explicitly prevents designers from embedding content served over HTTP.

Action

If a web content field shows up as blank, check that:

The web resource is accessible as expected through a web browser.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening the browser's developer console and monitoring the requests and responses going over the network:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, embedded interfaces, interfaces, web server, web services, network

KB-XXXX Web Content Field not rendering content

Jussi Lundstedt — Tue, 15 May 2018 18:46:53 GMT

Revision 1 posted to Appian Knowledge Base by Jussi Lundstedt on 5/15/2018 6:46:53 PM

Symptoms

When embedding content into a web content field, it fails to render in one of two ways.

The web content field is blank instead of rendering the expected page.
The web content field errors out with a pink box error.

Cause

Blank web content fields are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.

The pink box error is caused by attempting to embed insecure content served over HTTP rather than HTTPS. Appian recommends all Appian instances accessible over the Internet are secured with HTTPS. In order to minimize vulnerabilities arising from embedding insecure content in a secure Appian environment and to prevent browser errors arising from mixed content, Appian explicitly prevents designers from embedding insecure content.

Action

If a web content field shows up as blank, check that:

The web resource is accessible through your web browser as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening your browser's network developer console and monitoring the requests and responses:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, interfaces, apache, web server, web services, network

KB-XXXX Web Content Field not rendering content

Jussi Lundstedt — Tue, 15 May 2018 14:55:33 GMT

Revision 5 posted to Appian Knowledge Base by Jussi Lundstedt on 5/15/2018 2:55:33 PM

Symptoms

When embedding content into a web content field, it fails to render in one of two ways.

The web content field is blank instead of rendering the expected page.
The web content field displays a pink box error.

Cause

Blank web content fields are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.

Action

If a web content field shows up as blank, check that:

The web resource is accessible through your web browser as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening your browser's developer console and monitoring the requests and responses going over the network:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, interfaces, apache, web server, web services, network

KB-XXXX Web Content Field not rendering content

Jussi Lundstedt — Tue, 15 May 2018 14:55:18 GMT

Revision 4 posted to Appian Knowledge Base by Jussi Lundstedt on 5/15/2018 2:55:18 PM

Symptoms

When embedding content into a web content field, it fails to render in one of two ways.

The web content field is blank instead of rendering the expected page.
The web content field displays a pink box error.
>

Cause

Blank web content fields are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.

Action

If a web content field shows up as blank, check that:

The web resource is accessible through your web browser as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening your browser's developer console and monitoring the requests and responses going over the network:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, interfaces, apache, web server, web services, network

KB-XXXX Web Content Field not rendering content

Jussi Lundstedt — Tue, 15 May 2018 14:52:59 GMT

Revision 3 posted to Appian Knowledge Base by Jussi Lundstedt on 5/15/2018 2:52:59 PM

Symptoms

When embedding content into a web content field, it fails to render in one of two ways.

The web content field is blank instead of rendering the expected page.
The web content field displays a pink box error.

Cause

Blank web content fields are typically caused by the host server using response headers that explicitly restrict where content can be embedded. Typically, embedding restrictions are controlled by sending an X-Frame-Options header in the HTTP response from a web page. This can be set to either DENY to disallow embedding globally, SAMEORIGIN to allow embedding only within the same origin or an explicit domain to establish domains where content can be embedded. A blank page or a page with an error message can also arise if the site you are attempting to embed is unavailable, either due to being down or hidden from the public internet by IP whitelisting or VPN.

Action

If a web content field shows up as blank, check that:

The web resource is accessible through your web browser as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening your browser's developer console and monitoring the requests and responses going over the network:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, interfaces, apache, web server, web services, network

KB-XXXX Web Content Field not rendering content

Jussi Lundstedt — Tue, 15 May 2018 14:49:08 GMT

Revision 2 posted to Appian Knowledge Base by Jussi Lundstedt on 5/15/2018 2:49:08 PM

Symptoms

When embedding content into a web content field, it fails to render in one of two ways.

The web content field is blank instead of rendering the expected page.
The web content field displays a pink box error.

Cause

Action

If a web content field shows up as blank, check that:

The web resource is accessible through your web browser as expected.
The resource being embedded is accessible over the public Internet or configured to allow traffic from the Appian instance by either IP whitelisting or a VPN tunnel.
The source of the web content field does not send out a X-Frame-Options header that would block it from being embedded. This can be seen in the response headers of the web page, which can be accessed by opening your browser's network developer console and monitoring the requests and responses:

If a web content field errors out with the HTTP error, the source must be configured to use HTTPS.

Affected Versions

This article applies to Appian 18.1 and later.

Last reviewed: May 2018

Tags: web browser, interfaces, apache, web server, web services, network