如果请求时间太长，Rails 200状态代码将更改为302？

Question

I have a rails app that fires off some code to assemble a large report on all a users data. This takes ages and needs to come off an external API (salesforce).

I have code that works on many records:

• Grabbing the data
• Formatting it correctly
• Passing it to the view and rendering as a pdf before refreshing the page with ajax.

Most requests end like this:

Rendered record_requests/_get_digest.html.erb (2974.9ms) Rendered record_requests/get_digest.js.erb (2983.4ms) Completed 200 OK in 5957ms (Views: 2770.9ms | ActiveRecord: 222.1ms)

Which is great!

But some of the largest records can take 6+ minutes to grab and process - at which point something different occurs: ```

Redirected to https://[base_URL]/record_requests/5 Completed 302 Found in 288345ms (ActiveRecord: 2.4ms) This is also a disaster because the redirect seems to kick off the initial request again so i get stuck in a loop...

These two requests use exactly the same code!! Why is one getting rendered and the other getting redirected? Is there a built-in rails timeouts.

Soo confused, can anyone shed any light on this?

This all works via the very excellent Restforce gem,the full gemfile is listed here .

The controller looks like this:

# GET /record_requests/1 def show respond_to do |format| format.html {} # format.json { head :ok } format.js end end

# GET /record_requests/1/get_record def get_digest @client = @record_request.client_digest @request_digest = @record_request.build_request_digest respond_to do |format| format.js end end

Answer 1

If its pretty much exactly 600s it will be a timeout.

I would guess, possible sources are:

• salesforce itself, althought I can't see a mention of a specific timeout for requests
• the client library you use to call the api, and how you handle the reponse
• the webserver you host on

Of the three, as it's rails showing the redirect - I would guess it's the second one, but without the details of the code and library you use, it's hard to say - it depends on how you handle errors in that method.