Wt

As a follow-up to #2078, when an application calls setInternalPath() in progressive mode before enableAjax() has occurred, Wt will have the browser update the URL with a redirect to the requested URL --- adding a wtd so that it will get handled by the same session. Once added, this wtd remains for the life of the session. If the application has "reload-is-new-session" set to false, this is unexpected (from a user standpoint). Moreover, and I'm not sure if this should be considered a bug, a browser refresh in this state does not work correctly --- it appears unstyled.

In any case, removing the wtd from the URL after a redirect (when reload-is-new-session is set true) avoids the refresh problem, and seems to better mirror the bootstrap mode of operation.

I've attached a patch that removes a wtd parameter from the URL after a redirect. It seems to work in my limited testing, but would certainly benefit from additional review.

The patch is actually supplied in two parts. The first contains a patch to remove the wtd. The second addresses an edge case in createUrl where the params are initially empty (and it outputs an "&"). I'm not sure if this edge case occurs in normal operation, but it occurs with the wtd-removal patch, so I've added a second patch to address it. Without this second patch, a URL without parameters will incorrectly end-up with a suffix of "?&".