Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Added clarification

Problem

...

You configured a direct connection of WProofreader with AppServer (as described Option A: Binding of Static Files and Serving Service Requests by AppServer) on

...

If you install WProofreader directly on the server with Apache Tomcat, and your . Your application and WProofreader are WProofreader static files are located in different domains, for example, domain_name1.com and domain_name2.com and there is a CORS error in the console.  

Below is an example of such an error:

Warning

Access to font at 'http://domain_name1/wscservice/wscbundle/themes/fonts/opensans_bold/.../font_name.ttf' from origin 'http://domain_name2/' has been blocked  by CORS policy: No 'Access-Control-Allow-Origin' header is present on the request resource.

Solution

webspellchecker.com and webspellchecker.net, a CORS issue may occur. To solve this issue, add the Access-Control-Allow-Headers to enable cross-control origin requests to the Apache Tomcat settings (/conf/web.xml file). It should be Apache Tomcat that is used for processing of the WebSpellChecker static files.

tip
Panel
bgColor#fff
  1. For detailed instructions, refer to the CORS filter description.
Note
  1.  Note that the description varies depending on the Apache Tomcat version used.

Solution

  1. After adding the CORS filer with allowed origins, restart your Apache Tomcat.

Content by Label
showLabelsfalse
max5
spacesWebSpellCheckerServer55x
showSpacefalse
sortmodified
reversetrue
typepage
cqllabel = "apache_tomcat" and type = "page" and space = "WebSpellCheckerServer55x"
labelsIIS installation


Page properties
hiddentrue
Related issues

...