[
https://issues.apache.org/jira/browse/RAVE-772?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13440162#comment-13440162
]
Scott Wilson commented on RAVE-772:
-----------------------------------
On testing a bit further I can see that the problem isn't an issue with the
proxy at all, its a problem with JQueryMobile - the fragment identifier screws
up the JQM page view system. This seems like a pretty major problem if we can't
use OpenAjax with JQM.
> Wookie proxy URLs are broken in Rave
> ------------------------------------
>
> Key: RAVE-772
> URL: https://issues.apache.org/jira/browse/RAVE-772
> Project: Rave
> Issue Type: Bug
> Reporter: Scott Wilson
>
> If you use a Wookie widget that uses the server-side proxy, such as Twidget,
> you end up with an iFrame URL like this:
> http://localhost:8080/wookie/wservices/wookie.apache.org/widgets/twitter/index.html?idkey=cd03TmSPSK74cv.sl.gB3GVwdx1Hbo.eq.&proxy=http://localhost:8080/wookie/proxy&st=#rpctoken=cuXrOH&oahParent=http%3A%2F%2Flocalhost%3A8080
> The "#rpctoken=cuXrOH" section breaks the proxy URL and means the widget
> can't retrieve any data.
> I don't know where this fragment id is added, presumably its something that
> happens in the OpenAjax code?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
