I was expecting titanium proxy to catch XMLA requests sent from Excel (Analysis Services).
It does not appear to be the case. I am listening all IPs.
Anything I am missing or is it just not possible ?
Thx
Related
I am using tRestClient component in my Talend job to call a REST API. The REST API call is working fine when sent through Postman. But it is giving 500-Internal Server Error when executed through Talend job.
I want to investigate it further using Fiddler. Is there any special setting I need to do in Fiddler?
Place a tSetProxy before the tRestClient, and set your fiddler proxy address and port so that traffic goes through Fiddler.
For me it's localhost 8888.
I am using Apex (Force.com) to send HTTP requests to a server that is hosted on AWS. How can I know if the server I am sending the HTTP request is using a valid certificate and my request will be encrypted before being sent out? I know I'd be able to look for the lock icon on the browser but since this is a RESTful API callout, I'm not sure how to do that. I found one similar question here and the answer seems to be PHP specific.
Message Analyzer Tool would help you here and this tool will track all communication including encryption.
Please install Message Analyzer tool in your client OR server environment and track the message.
Please check this link - https://technet.microsoft.com/en-us/library/dn727244.aspx
Regards
Abdul
As i understand from documents, zabbix has made it possible to monitor SOAP web service by using custom headers from v2.4. but it has no clear explanation on how to do this!!can anyone explain more about this?
UPDATE: i have SOAP web service on a port on my localhost.can i monitor it's performance using zabbix 2.4?!
SOAP request usually needs custom header, e.g.:
Content-Type: application/soap+xml
You can define this custom header(s) in the Zabbix 2.4 Webmonitoring. But keep in mind, that Webmonitoring is executed from the Zabbix server (or proxy) only. Make sure, that your soap server is reachable from the Zabbix server (proxy) and only then you can use Webmonitoring. Otherwise (if service is localhost only) you have to use checks, which are executed from the zabbix agent (net.tcp.service.perf, UserParameters) and in that case you can have a problem with headers.
It depends how deeply you want to monitor your SOAP service. If it's only http connection time, then you don't need a Webmonitoring (net.tcp.service.perf is enough). If you want create some special SOAP request with response content check, then Webmonitoring is right choice for you.
Docs:
https://www.zabbix.com/documentation/2.4/manual/web_monitoring
https://www.zabbix.com/documentation/2.4/manual/config/items/itemtypes/zabbix_agent
I'm trying to use a sample web application that use Ajax to send a request to a php REST service.
I need to use Mule ESB to do this, so i fix my ajax function to send request to ESB on localhost:8080. But the browser said that i can't do this for security reason.
So, there are any way to use mule ESB with a web app (local appache server) locally ?
Trying to GET a resource from the same host but from a different port is considered cross scripting as explained here
If you want to retrieve it you can:
all the option listed at the above link
put mule behind a reverse proxy within your apache configuration
serve all the content via mule
I am implementing XMPP service in the browser using BOSH. I use JAXL library. I am able to manage the connection over BOSH to my localhost server (ejabberd). The session is started and the user is authenticated with no problem. However, when I just change the BOSH host to jappix.com, the very first response from the server is only empty body. Even if I repeat the request (according to XEP-206) I still get only empty body so I'm unable to perform any other actions.
So that's my question: Is it possible to use jappix.com to handle my BOSH requests? Are there any limitations? How can I fix this issue? I'll provide more information if needed.
I am the Jappix.com owner!
Your question does not concern our service directly but more likely a node-xmpp-bosh - the BOSH server we are running - bug (?) that you can report on http://code.google.com/p/node-xmpp-bosh/