I have a ASP .NET Core MVC web service hosted in Azure to which I would like to POST data. I am able to post from Postman so I know the service is working and the required format of the request. I have another client sending what I believe to be the same post request but somewhere the request is failing. I would like to confirm the requests are reaching the service and if so see exactly what the request looks like when it gets there so I can compare to the working version. I have enabled web logs on the service but what info I can find as a result does not provide detail of the failed request. I also downloaded logs via the Cloud Explorer in Visual Studio but again I cannot see the content of the request to troubleshoot. I'm sure I'm not utilizing the logging fully but I'm not familiar enough with Azure web services to know what I'm missing and am having trouble finding guidance on the web. Perhaps it is not possible to capture the failed post data for security reasons? If so then presumably I need to hook up a debugger and see if I can step through the processing of the request.
What would be the most effective way to troubleshoot failed web service requests?
After further research I found an excellent reference on troubleshooting Azure Web Services at https://learn.microsoft.com/en-us/azure/app-service-web/web-sites-dotnet-troubleshoot-visual-studio. Using the information and tools covered there I was able to resolve my problem which ultimately proved to be a problem sending the request. Watching the web server logs it became clear the client's request was never reaching the server.
Related
We got a lot of failed requests throwing from Get /echo/resource in the Azure application insights, I could not find it in our .net projects (for the rest failed APIs I can find them in the code), also When I launch the project in the browser, with using the developer tool, this echo API is not in API lists under Network tab. Below are the screen shots captured from the application insights:
APIs error list sample
transaction detail of echo/resource error
I googled and get the basic info about what is echo, but not quite sure if we are not using it in the .net project, where it comes from?
Based on the path of URL, it seems to be coming from the API Management placed before your REST API application. APIM has the default Echo API for testing purposes. This API seems to have been configured/exposed or is being used to route the request to the backend App itself.
I'm a newbbie to Fiddler, and I really need it in my web debugging. I tried to search for how to use it, but there is no much useful topics on this, may be due to its easiness!
What I'm trying to do is to capture the session from my Web API service. However, as soon as I start the service in Fiddler, it starts to capture a lot of sessions, and keep adding to its list, none of them seems to be what I requested.
I'm following a tutorial on YouTube, where the tutor starts the service and issue a GET request and Fiddler stores just this session.
Is there any configuration I can do to get it working like that?
This is what Fiddler looks like when I start the Web API service:
EDIT
I used filters to block sessions from vshub, but still not getting any records for the service at all!
I'm new to IBM BPM and am trying to put together a process that sends a POST request to a RESTful web service using teamworks.HttpClient.
I am able to POST via Chrome's Advanced REST Client, so I know the server and service are accessible from my system.
When I try to do this via teamworks.HttpClient in Process Designer I get HTTP Status 405. I've only ever seen that when I screwed up and specified GET.
I have written Ajax calls in JavaScript to access this service. I have had to specify POST in the Ajax calls.
Is teamworks.HttpClient configured to be a GET or POST by default? If it does GET, how can I tell it to do a POST?
If I understood correctly what you did, your assumption is correct: teamworks.HttpClient fires a HTTP GET by default. As far as I know, there is no way of configuring it to send a POST request.
I would recommend writing your own Java Integration Service with a more capable web client, this will be really handy for the future anyways:
http://www.ibm.com/developerworks/bpm/bpmjournal/1404_boyer/1404_boyer.html
This resource includes writing your own REST Server, but at the bottom there is also a chapter about implementing a REST Client as a Java Integration Service.
I've got a small ASP.NET web site, that calls another company (somewhat) Restful web service. My site has no logging currently. Is there an online service that can proxy all calls from my site and provide error logging and possibly retry functionality?
Have you tried https://ngrok.com/ - For local development, it's probably exactly what you're looking for.
If you just want to inspect the traffic your system is sending out or receiving, http://www.telerik.com/fiddler is a good choice.
hi i have developed a application, that works fine on the simulator, now i want to test the application on the actual device.
my application tries to access web services over the internet. I mean to say, the application makes SOAP request to web services. Also i am accessing the web services using https
So in this case, do i need to first sign the application.
if not, then how do i go ahead, with deploying the application.
i tried deploying the application, using the blackberry desktop manager, the application got installed, but it is not making calls to web service.i mean to say, the application is not hitting the web service
Are you getting any error messages from the application? If you need to sign any API's then you'll receive an error.
Use the Blackberry Browser to check if you can hit the webservice. Sometimes there can be issues if your handset is on a BES or if the webservice is behind a firewall.
Check that you have connections or it will timeout.
For https connection you can refer to foll. post :
http://supportforums.blackberry.com/t5/Java-Development/Connecting-your-BlackBerry-http-and-socket-connections-to-the/m-p/206242
This issue has to do with some MDS servers having a low default for how large the requests they can pass through are:
http://supportforums.blackberry.com/t5/Java-Development/HTTP-413-Request-Entity-Too-Large/ta-p/445983
Still trying to sort out a good solution to this myself for a service that returns a large XML packet since it can't be reliably known whether a user's service has the default minimum or something higher.