Currently, we are using GetHttpRequestData().headers to get real IP address of User. However, we are facing following issue. when we try to call SOAP web service request, we receive following error Premature end of file. I already searched the web and found out that there is bug in ColdFusion 8.0.
I don't know if this bug is resolved yet.
Is there any alternate solution?
Please help me.
thanks
Is the SOAP request coming in to ColdFusion from a client and that is where you are getting the error or is a user hitting a coldfusion page that is then making a soap request to some other service and that is generating the error?
We had the exact same issue. I don't know if you've found a solution yet but the workaround I found is using getPageContext().getRequest().getHeader("name of header here") to retrieve the request header I'm looking for. This doesn't break to SOAP calls like getHttpRequestData.
Related
What is the difference between the way a browser calls the URL and doing it via Rest Debugger or HTTP Components?
I have a 3rd party Web REST API that work every time in a browser (IE it returns JSON as expected), but when I use (GET) the same URL in the Delphi REST Debugger it returns error code 429 Too Many Requests.
I am not allowed to post the exact URL here (I'm sorry, boss has the last say but it is like this https://xxxx.yyyy.com.au/search/resources/store/zzzzz/productview/123456).
For additional information the result is consistent giving the 429 error when I use NetHTTPClient and NetHTTPRequest components as well as using the Delphi REST Components.
I thought that setting the user agent to be the same as my browsers might help, but alas it didn't. I use Delphi 10.3.3 Rio
I'm a bit new to REST and haven't found an answer by googling for a couple of days now. Any help will be most appreciated.
Thanks,
John
The answer is cookies. When I rejected all cookies I could see the behavior as stated by #RemyLebeau where the page is in a continuous loop. The browser sends a cookie with the request header. I'm new to all of this, so I'll try to replicate what the browser is doing and see what happens. If I get really stuck I'll post another question specifically about cookies. Many thanks to all who offered advice. Most appreciated. I put this here because someone deleted this as an answer.
I am getting started on an API testing project using supertest, mocha and chai. I am using postman to manually send the requests first to ensure they are working before writing the code for them.
All my get and post commands are working successfully except for this patch request. This is the first patch request I am attempting to send.
Request Headers
Request Body
Code
First request is passing, second is failing
The URL's are identical so I know they are valid and the authorization is working correctly.
I feel that as the first command is passing this is not a sync issue
This definitely needs to be a patch request according to the swagger
I'm new to API testing so would greatly appreciate any insight anyone may have into this issue.
Well nobody ever likes to hear it but it appears my problem has resolved itself after leaving it for a day.
I really wish I had an understanding of why this has happened but for now it appears I will have to go ahead unsure of what caused it or how it was resolved.
I am using BinarySecurityToken for OTA_AirRulesRQ, but I am getting USG_AUTHORIZATION_FAILED. I used the same token for BargainFinderMaxRQ and it worked. Is it some problem with the SOAP request I am sending or access to this method is not authorized form my PCC ?
Also I am able to hold PNR and Issue ticket with same credentials
Please Suggest
You should contact the API helpdesk providing your credentials
Do you point it to the according endpoint. E.g. getting creds from prod/testing and using it in prod/testing?
Can you post the message you are trying to send including headers. You can block out Pcc information, but it would help to see the message. It may be something simple you are overlooking and at the very least I could duplicate the call on my test bench and try to to duplicate the issue.
I want to love the v3 API. Unfortunately, when making the seemingly simple call:
service.executeQuery("select * from TimeActivity");
I get the crushing reply of:
<Error code="6002">
<Message>message=Timeout occurred while proxying request; errorCode=006002; statusCode=504</Message>
</Error>
What kind of problem could cause this?
Typically a 504 error code indicates there is a dependency timeout. It is clear that the server you are contacting is responsive, as you are receiving the response.
This kind of error is common if there is any kind of fault in the back end of the server or some service they rely on has gone down. You may want to contact the system administrator or responsible support team to ask about this, as it's likely affecting anyone accessing the same service as you.
It looks like something is wrong with my account. All TimeActivity queries fail in the API explorer. To Intuit support I go!
Has anyone got a sample SOAP payload for the ideone.com service?
I've tried several clients including the Firefox SOA client ( which returns an error from the service), the 360Works java soap client which crashes on reading the wsdl, and the online soapclient.com which returns nothing.
I tried two of the SOAP clients you mentioned, soapclient.com and Firefox SOA, and successfully accessed the service at ideone.com.
First, make sure you are using the API password when trying the service and not the site password.
With soapclient.com, make sure that you're viewing the results as XML. You won't see anything if you choose HTML (one of their options).
With both clients, make sure you don't interpret the status with a key name of "error" as meaning that an error has been returned, if the value of this field is "OK". This indicates success.