Hi there
Error 503 is a red herring..
I use a HTTPUtils2 to send HTTP requests to a server and await responses. I have a service triggering these requests periodically every 5 minutes. I do manually trigger the service on login and can trigger it with a button press. When I manually trigger the service by logging on or pressing the button I get the correct responses sent back 200 and 304.. but when I leave the device alone and let it run the service after setting StartServiceAt then the HTTP request is made but comes back with a 503 error. It seems not to send it from the device but just send it and not get a response so gives an error 503. I have a colleague who can see no trace of the request being sent from the device in Fiddler.. Can anyone advise what might be going wrong?
Thank you,
Derek.
Error 503 is a red herring..
I use a HTTPUtils2 to send HTTP requests to a server and await responses. I have a service triggering these requests periodically every 5 minutes. I do manually trigger the service on login and can trigger it with a button press. When I manually trigger the service by logging on or pressing the button I get the correct responses sent back 200 and 304.. but when I leave the device alone and let it run the service after setting StartServiceAt then the HTTP request is made but comes back with a 503 error. It seems not to send it from the device but just send it and not get a response so gives an error 503. I have a colleague who can see no trace of the request being sent from the device in Fiddler.. Can anyone advise what might be going wrong?
Thank you,
Derek.
Last edited: