When attempting to trigger a data load via the directions found at http://msdn.microsoft.com/en-us/library/gg585130 I run into a 404 response. I've read over it several times and I keep coming back around to the same issue I was wondering if something has changed with the latest deployment or if I am doing something wrong... I have inlcuded the rest call that I am trying to make below... minus my Api Key.
http://spatial.virtualearth.net/REST/v1/Dataflows/LoadDataSource?dataSourceName=StoreDetail&loadOperation=complete&dataLocation=http%3a%2f%2finternaldevelopment.blob.core.windows.net%2fstoredata%2fDSFStoreData.xml&input=xml&output=xml&key=
Any help that can be offered would be greatly appreciated.
The problem that I experienced was related to the issue that I had failed to include the following values as part of the request headers during my rest call.
Expect: 100-continue
Connection: Keep-Alive
Related
I have some rest and GraphQL services works with ruby and typescript (with nestjs framework).
I've noticed that a couple of days ago some of the POST requests failed due to params validation error.
After further investagaion, it seems like on some requests the body params sphoradicly drops from the requests somewhere on the network. It happen for small amount of requests (less than 1%).
This issue started when no changes deployed on the server or clients side. My clients are iOS and android apps and it happens for both platforms.
I've tried to find the exact point on the network that the body dropped, with no success.I've also tried to find a solutions to similar issue on the net.
Does anyone have any idea what can it be? I haven'e found any relevant information about similar issues.
Thanks!
I'm experiencing an issue using Sophos Labs Intelix Dynamic file analysis: https://api.labs.sophos.com/doc/analysis/file/dynamic.html
For some files submitted, the API returns 202 for several minutes, then returns 404, as if the job is suddenly lost. There is no explanation or report provided. I did not experience this issue until this morning when suddenly it happened for 7 different files, although we have not made any code changes.
Why is this happening and what are we supposed to do to handle it?
Some example dynamic analysis jobIDs which now return 404: 10c37c488e86b6871c3f6224ff5273e1, bc900e7bfb8bb25e1f8f127dc25ab8fe, 48cda26c2e3cb54d0b3f4b79ac1ddb7e
Also, is this the correct forum for support requests? I am also trying to go through https://support.sophos.com/support/s/sophos-technical-support but they don't seem to have any knowledge or understanding about Intelix API. My credentials for the API don't appear to be linked to any kind of support portal?
Thanks!
I am using Hoplon to create a fairly simple site and an stuck on the AJAX part. In the past I have used Castra as the backend but since it is no longer maintained I have switched to a normal LuminusWeb backend. I am in need of making a call to the server in which I will the server and then wait for a response. I know how to do it on the server side but I can't seem to find any information about how to do it on the Hoplon Client side.
How can I send a request to the server using an AJAX call?
I know how to do it in jQuery and assume, possibly wrongly, there is something similar to $.POST in Hoplon.
Cheers
The best way to solve this AJAX problem that I found is to use the library 'cljs-http' and then you can make an synchronous request using a call such as:
(http/post "http://localhost:8080/" {:with-credentials? false})
Then, on the cljs-http GitHub README.md it gives plenty of examples so you can then do asynchronous in Hoplon.
First time posting a question. I'm trying to call some SOAP webservices from inside a blackberry app using the ksoap2 library. I've successfully managed to get a response from the one service, which uses an HTTP url, but now that I'm trying to get response from a (different) HTTPS url, I've run up against a brick wall.
The response dump I'm getting has the following fault message:
"An error occurred while routing the message for element value : (country option I specified in my request). Keep-Alive and Close may not be set using this property. Parameter name: value."
The weird thing is that using Oxygen XML's SOAP tools with the XML request dump works just fine. Any ideas where to start looking? This has taken up a full day already.
Update:
Responding to your comment below - it turns out the double quoting is part of the SOAP spec. Some servers are more relaxed in their implementation, and will work without the quotes.
ksoap2 doesn't force the quotes onto your actions - you may want to patch your ksoap2 library to ensure the quotes are always there.
ymmv
Original:
I don't think this is a SOAP related problem, nor with BlackBerry.
I think the problem lies on the server side, since that error string is not a common error (just google it to see no hits on the whole internet other than this question).
Looks like this is a job for the network guy on the server side to tell you what he's seeing on his end.
Only other thing I can think of is to make the call using HTTP instead of HTTPS. You can then use some network sniffer to see what the difference between the messages is. Alternatively, install an SSL proxy with something like "Charles" and sniff the packets like that.
I have my script email me when there is a problem creating a recurring transaction with authorize.net. I received the following at 5:23AM Pacific time:
SOAP-ERROR: Parsing
WSDL: Couldn't load from 'https://api.authorize.net/soap/v1/service.asmx?wsdl' :
failed to load external entity "https://api.authorize.net/soap/v1/service.asmx?wsdl"
And of course, when I did exactly the same thing that the user did, it worked fine for me.
Does this mean authorize.net's API is down? Their knowledge base simply sucks and provides no information whatsoever about this problem. I've contacted the company, but I'm not holding my breath for a response. Google reveals nothing. Looking through their code, nothing stands out. Maybe an authentication error?
Has anyone seen an error like this before? What causes this?
Maybe as a back up you can cache the WSDL file locally and in case of network issues use the local copy. I doubt it changes often so if you refresh it weekly that should be satisfactory as the file will probably not be stale by then.