1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
|
-
+
-
+
-
+
-
+
-
-
+
+
-
+
-
+
-
+
|
Hints For Debugging Wapp Applications
Hints For Debugging W3 Applications
=====================================
Here are some suggestions for debugging Wapp applications:
Here are some suggestions for debugging W3 applications:
+ If it seems like the [wapp-param](commands.md#wapp-param) command is not
+ If it seems like the [w3-param](commands.md#w3-param) command is not
working correctly, that might be because the same-origin policy
is preventing query parameters from being parsed.
Try adding the [wapp-allow-xorigin-parameters](commands.md#allow-xorigin)
Try adding the [w3-allow-xorigin-parameters](commands.md#allow-xorigin)
command to the top of the page generator proc, at
least temporarily, to see if that clears the problem.
+ If parts of your webpage do not appear to be working, that might
be due to the restrictive default
[Content Security Policy (CSP)](https://en.wikipedia.org/wiki/Content_Security_Policy)
that Wapp uses. Try temporarily disabling the CSP using a command
like <blockquote><b>wapp-content-security-policy off</b></blockquote>
that W3 uses. Try temporarily disabling the CSP using a command
like <blockquote><b>w3-content-security-policy off</b></blockquote>
near the top of your page-generator proc.
+ Temporarily insert the output of the
[wapp-debug-env](commands.md#debug-env) command in your output to see
[w3-debug-env](commands.md#debug-env) command in your output to see
what is going on. Example:
> >
wapp-trim {
w3-trim {
<h1>Environment</h1>
<pre>%html([wapp-debug-env])</pre>
<pre>%html([w3-debug-env])</pre>
}
|