Re: SubmitCompleteEvent behaves differently on deployed server than it does on local environment

Welp, turns out the response is wrapped in an HTML <pre> element even though the response type is text/plain. Bah! I've been pounding my head against this for hours but at least I know what to do to fix it. Thank you for your help, Jens.

On Tuesday, May 10, 2016 at 3:53:46 PM UTC-4, Matthew McLarty wrote:

First of all, thank you for your input. I appreciate it very much :)

I just checked in an update to throw up an alert box of what's being returned as the SubmitCompleteEvent and SubmitCompleteEvent.getResults() so I will know that as soon as my dev server finishes building.

The response headers are fairly similar. In the screenshot the top set are from my local environment and the bottom are from the remote server. I'm totally grasping at straws here. I have no idea what could be causing this. I had read some things about servers defaulting to text/html instead of text/plain and that throwing some odd issues at people but it doesn't appear that my remote server is configured to do that. Maybe I should set the content-type? 

On Tuesday, May 10, 2016 at 3:39:16 PM UTC-4, Jens wrote:

I guess response headers are different. Have you compared them? You have only showed the response body.

Also whats the actual result of event.getResults() in both cases? If you haven't implemented it differently GWT will submit your form into an iframe and the browser might wrap the response using <pre></pre> for security purposes.

-- J.

--
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 https://groups.google.com/group/google-web-toolkit.
For more options, visit https://groups.google.com/d/optout.