Hi Stu, Thank you for the feedback.
I would recommend replacing line 57 HttpContext.Current.Session["WebServiceUrl"] = HttpContext.Current.Request.Url.Scheme + ":" + "//" + HttpContext.Current.Request.Url.Authority + "/cms/WebService/RqlWebService.svc"; to HttpContext.Current.Session["WebServiceUrl"] = HttpContext.Current.Request.Url.Scheme + ":" + "//localhost/cms/WebService/RqlWebService.svc"; Because having the function there is to address another compatibility issue. If CMS was installed as HTTP, and SSL was added later, then despite the user accessing via HTTPs, the webservice is only accessible via HTTP. If CMS was installed as HTTPs via the installer, then the webservice is only accessible via HTTPs. The function is trying "smartly" figure out where is the webservice based on the user's URL. Hard coding the webservice URL may work for one client, but not another. Again, I appreciate your feedback and it is exactly the information I need to improve the RQL connector. Best, -Jian On Monday, February 24, 2014 7:11:40 AM UTC-5, Stu Wilson wrote: > > Jian > > Thanks for that. > > Removing the whole function and replacing with a static string fixed the > issue both remotely and internally. > > I have at least discovered the reason for the latter issue, i.e. case 2. > > It was the XS protection built into the app. Section 2.7.7 of the install > notes refers to the solution. A couple of notes that I hit, that other may > get caught out on. > > main.config - this is not the main.config in the MS\Configuration folder, > it's in the MS\Asp folder > > You need to perform an IIS restart for the changes to the config to get > updated. The obvious restrictions that imposes may hit systems with 24/7 > usage. > > Stu Wilson > > On Friday, 21 February 2014 08:41:20 UTC, Stu Wilson wrote: >> >> This is probably a Jian question, but I'm open to other solutions. >> >> On a new installation 11.2, I'm having issues running any plugins from a >> machine external to the server. >> >> In case 1, the plugin opens and appears to run, but time out when trying >> to retrieve data and return 0 results. I believe this is due to the >> http/https issue with the RQL Connector that Jian has been fixing recently. >> >> a) accessing the CMS and the plugin from the CMS server on >> https://localhost/cms and running the plugin works just fine. >> b) accessing the CMS and the plugin from an external machine on >> https://cms.domin.com/cms and running the plugin fails >> >> I have this issue with Check Multi Page Connection, Retroactive >> References 2, and Delete All Unlinked Pages 2. >> >> All the plugins are up to date from Jian's Git repository. >> >> >> >> In case 2, parts of plugins cause 403 errors when clicking events "(RQL >> Console" "session" button") >> >> This happens regardless of where I am accessing the Plugin from. I'm >> guessing that for some reason the session variables are not being shared >> across to the popup window. >> >> Thx for checkign this out >> >> Stu Wilson >> > -- You received this message because you are subscribed to the Google Groups "RedDot CMS Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to reddot-cms-users+unsubscr...@googlegroups.com. To post to this group, send email to reddot-cms-users@googlegroups.com. Visit this group at http://groups.google.com/group/reddot-cms-users. For more options, visit https://groups.google.com/groups/opt_out.
