No, Caja doesn't have special requirements of the web server its files are on.
Oh, but maybe you have a cross-origin policy. If you're trying to load content using Caja from a third-party site (rather, one with a different domain name), then either you need to use a proxy (there's one supplied with Caja, but it's a bit of a mess), download the content via your own server first and provide it to Caja as a string, or have the other site allow access via CORS (Access-Control-Allow-Origin header). If that's the problem, then there will be a message in your JavaScript console complaining about the lack of Access-Control-Allow-Origin. If that's not the problem, we'll still need more information to go on. A complete copy of what's in the JavaScript console on the page that's trying to use Caja would be a good starting point. On Sat, Mar 21, 2015 at 10:10 AM, Vasilis Sikkis <[email protected]> wrote: > > Does the server needs to have any special requirements? Can you provide > me with an example with a code that is not provided in the caja server? > > -- > > --- > You received this message because you are subscribed to the Google Groups > "Google Caja Discuss" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "Google Caja Discuss" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
