Monday, November 2, 2015

GWT browser plugin not used with Web rewrite rules?

I am using html 5 push and as such perform some rewriting in the apache web server to ensure that all urls that not point to an existing file or directory, are changed to  /index.html.

However, if I do this, the Firefox GWt plugin isn't used anymore. Why ? How and when is the GWT browser plugin being triggered/used?

My apache config part:
<Directory "/Users/ed/Develop/Web/plus" >
  RewriteRule ^plus/$ - [NC,L]
  RewriteRule ^plus/index.html$ - [NC,L]
  RewriteCond %{REQUEST_FILENAME} !-f
  RewriteCond %{REQUEST_FILENAME} !-d
 RewriteRule plus/(.*) plus/index.html [NC,L]
</Directory>

The url that work fine, because the last rewrite isn't used (seen in the apache log with rewrite trace enabled):
 http://localhost/plus/bla1/index.html?gwt.codesvr=127.0.0.1:9997

The url that doesn't work, because the last rewrite is used:
http://localhost/plus/bla1/index.html?gwt.codesvr=127.0.0.1:9997

The index.html is started, and will show the "loading..." text, that is normally removed when the GWT app is started and will remove it. However, the gwt app is never started.
No idea why, the query param part is copied by default (accoding to the apache 2.4 doc).
Please some help? (why/how is the gwt plugin triggered to start working).
- Ed

--
You received this message because you are subscribed to the Google Groups "GWT Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to google-web-toolkit+unsubscribe@googlegroups.com.
To post to this group, send email to google-web-toolkit@googlegroups.com.
Visit this group at http://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.

No comments:

Post a Comment