Celebrate Excellence in Education: Nominate Outstanding Educators by April 15!
Found this content helpful? Log in or sign up to leave a like!
I am getting a 403 error on the job endpoint specifically. Please see the message below
**********************
Got response: HTTP/1.1 403 Forbidden [Server: CloudFront, Date: Fri, 22 Mar 2024 13:53:34 GMT, Content-Type: text/html, Content-Length: 915, Connection: close, X-Cache: Error from cloudfront, Via: 1.1 0a2ce08fa1ec3c33302a7547d3305978.cloudfront.net (CloudFront), X-Amz-Cf-Pop: SEA19-C1, X-Amz-Cf-Id: AmE9ZCc8r-Hu1UQBZZsdhSE3awBoIREAdVqOoTd3d5uQdN7bjXqhDg==] [<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner
*****************************************
I am able to authenticate and successfully call all endpoints leading up to the job endpoint, including the POST to start the /query/ jobs and the GET /schema endpoint. I am just working on how best to poll those jobs to make sure they all finish before trying to retrieve the complete files. Any help anyone can provide would be greatly appreciated.
Thanks,
James
Please note title should say 403 not 402. I tried to correct it, but it would appear not to allow a change to the title after reaching the main submission page.
@jsmith141 We've had situations in the past where the access token would time out on a very long running job (we weren't refreshing tokens at the time) and checking status would eventually result in an "unauthorized" response for things that ran more than 60 minutes. Not sure if that's the case in your situation, but it is worth a look if things are taking a long time.
@mclark19 Thanks for your reply. It is well under an hour. I pretty much see the 403 when I get to that /job call.
Here is the latest return I got after running just now. It really makes me think it is an issue on Canvas 2 side, see the text in bold...
Got response: HTTP/1.1 403 Forbidden [Server: CloudFront, Date: Tue, 26 Mar 2024 20:30:14 GMT, Content-Type: text/html, Content-Length: 915, Connection: close, X-Cache: Error from cloudfront, Via: 1.1 4dbcbae01dbe8e38ad716ec4b04c5f38.cloudfront.net (CloudFront), X-Amz-Cf-Pop: HIO50-C2, X-Amz-Cf-Id: OTwPRtTAbme2dcWIiaYaMFnXE5AWSYV-oLWldVonPSCitMpK7s-Ikw==] [<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> <HTML><HEAD><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1"> <TITLE>ERROR: The request could not be satisfied</TITLE> </HEAD><BODY> <H1>403 ERROR</H1> <H2>The request could not be satisfied.</H2> <HR noshade size="1px"> Bad request. We can't connect to the server for this app or website at this time. There might be too much traffic or a configuration error. Try again later, or contact the app or website owner. <BR clear="all"> If you provide content to customers through CloudFront, you can find steps to troubleshoot and help prevent this error by reviewing the CloudFront documentation. <BR clear="all"> <HR noshade size="1px"> <PRE> Generated by cloudfront (CloudFront) Request ID: OTwPRtTAbme2dcWIiaYaMFnXE5AWSYV-oLWldVonPSCitMpK7s-Ikw== </PRE> <ADDRESS> </ADDRESS> </BODY></HTML>]. The original request: GET /dap/job/a958e53c-5ba8-48ad-a16d-1ac6b8c4c3df HTTP/1.1 [Accept: */*, Authorization: <--Hidden-->, Content-Length: 4, Content-Type: text/plain; charset=UTF-8, Host: api-gateway.instructure.com, Connection: Keep-Alive, User-Agent: snaplogic/main25112 httpcore/36.0 (11.0.17), Accept-Encoding: gzip,deflate] [null]
To participate in the Instructure Community, you need to sign up or log in:
Sign In