Using the EWS managed api, (ExchangeService and etc), how can I view the actual SOAP of requests/responses without using a proxy?
If I get an error from the api, how can I view the contents of the packet?
You can use tracing see https://msdn.microsoft.com/en-us/library/office/dn495632(v=exchg.150).aspx that will output the request and responses sent/receive. The other thing is if you compile you own Dll from github https://github.com/OfficeDev/ews-managed-api you should be able to debug the error if its a parse issue on the receive side.
Related
i am trying to get Model Strucuture data of BIM360 Model That we store, for that i'm using metadata api passing threelegged Token, model urn, model guid, but getting 404 (Not Found Error). i tried for get model that we store in our bucket that we are getting from this api, but that model we stored in BIM360 Accounts for that API is giving Error of NOT Found,
i have passed all scope, backet:read, data:Read etc. couldn't getting result.
Thank you
It's a bit difficult to guess what's wrong with the limited information but generally, the 404 Not Found error would indicate that something in the URL (of the request made by the derivativesApi.getModelviewMetadata method call) is missing or wrong.
I'd suggest to look at the following:
Could you take the URN, GUID, and access token, and make the request to the GET {urn}/metadata/{guid} endpoint directly using some 3rd party client application such as curl or postman?
If this returns 404, there might be some issue with the actual URN and/or GUID
If this works, there might be some issue in your code
What Forge SDK exactly are you using, and for what language? Is it one of the official SDKs, or is it a 3rd party one?
Are you sure you're passing in the right parameters to the derivativesApi.getModelviewMetadata method call?
We have a REST API hosted on WSO2 API Manager. When calling the API through WSO2, it sometimes returns the correct response, other times gives an error that the json object received is invalid. The log file shows that the json request object is not being submitted to the API at all.
Can anyone help out on how to resolve or troubleshoot this issue?
I don't see any errors in the product log. The only difference I can see is the Activity Id is different in 2 requests, and it results in different responses.
I'm trying to develop a simple NodeJS web app that can more or less replace the Cloud Foundry (CF) CLI. I'm following the API documentation to send the application.zip to the CF Service, however I get an error response Unsupported Media Type.
For the application part of the body I'm sending the application.zip file that is uploaded from the browser.
For the resources part of the body I'm sending an empty Json array. My understanding is that as there is nothing uploaded initially there are no pre-uploaded resources that I want to specify, hence the array is empty.
With the Unsupported Media Type response, I suspect you send invalid request headers to the API. There is a CloudFoundry API client written in node.js and you may read the source code to see how they upload the app code.
If that does not help you, please refine your question and add some code that you have.
I am setting up a simple Google App Script to get some data from a spreadsheet to an external app. When I open the url from my browser or curl I get the proper JSON response.
See for yourself, here is the url:
https://script.google.com/macros/s/AKfycbwUqrOsqQk4rk0lY97Wl4bRsHVk6_CMVPz3hGHeyc3H2ZCahCIY/exec
You should get a JSON response. I would like to have a node app make a request to that URL and parse the JSON response. I am attempting with two different clients, restler and request, and with both I get this error:
Error: 140735264762208:error:0607907F:digital envelope routines:EVP_PKEY_get1_RSA:expecting an rsa
key:../deps/openssl/openssl/crypto/evp/p_lib.c:288
Any recommendations?
I believe this is a known Node.js issue that there is already a fix in progress for - https://github.com/joyent/node/pull/4827
I have written a mosync application that interacts with a REST we service. I am using the AMDownload package. Wat is the right way to send the json payload required by the REST API?
The HTTP 400 Bad Request perhaps happens because the MoSync Android runtime messes up the URL, causing the server to return this error. Alternatively, perhaps the MoSync Android runtime considers the URL to be wrong, and sends back the HTTP 400 Bad Request.
Is it possible for you to test on an Android device? To see if the result is the same.
Also, is it possible to find the exact URL/data sent to the server? Perhaps using some network monitor software. If you have access to the server, can you see the request it receives? If you would enter the same request in a client like the Firefox RESTClient, do you get the same response?