2022.2

<pinElm1>
<pin _idx=0>
<left>122</left>
<top>253</top>
<type>dent</type>
</pin>
<pin _idx=1>
<left>361</left>
<top>341</top>
<type>dent</type>
</pin>
</pinElm1>
</values>
HTTP Server Input plugin preferences 2
The second set of HTTP Server Input plugin preferences is used to enable serving static HTTP
resources, as part of an HTTP Server workflow. These resources are referred to within the HTML
response file and do not pass through a process to get served so the process is very quick. Static
resources are especially useful for additional formatting of HTML files such as JS (JavaScript) scripts,
CSS files and images, since they are not dynamic and generally shared between multiple dynamic files.
l
Serve HTTP resource: Check to activate static resource serving.
l
Resource action name: Enter a name that will be simulated as a folder in your HTTP struc-
ture. For example, if you enter images in this box, you would refer to any files in this folder
as href="images/file.ext" .
l
Resource folder: Type the path of the folder where your resources are located, or click the
Browse button and choose the folder in the browse dialog.
Note: Subfolders are accepted in the structure, so if your resource folder contains a folder
called faces, you could refer to a file in this folder as href="images/faces/johnsmith.jpg".
l
Capture OnTheGo group
l
Authentication Key: Enter the authentication key for the COTG repository. This key can
be found in the Settings section of the COTG Web Administration Panel.
l
Cross-Origin Resource Sharing (CORS)
l
Allowed Origins: Enter an origin (everything in a URL before the path, e.g. http://www.ex-
ample.com). The Workflow server will add this value to the Access-Control-Allow-
Page 662