http-status-codes

I want to be able to validate a form to check if a website/webpage exists. If it returns a 404 error then that definitely shouldn't validate. If there is a redirect...I'm open to suggestions, sometimes redirects go to an error page or homepage, sometimes they go to the page you were looking for, so I don't know. Perhaps for a redirect there could be a special notice that suggests the destination address to the user. The best thing I found so far was like this: $.ajax({url: webpage ,type:'HEAD',error:function(){ alert('No go.'); }}); That has no problem with 404's and 200's but if you do

The HTTP/1.1 standard states that if a POST operation results in the creation of a resource, then the response should include a Location header with the address of the new resource. If a resource has been created on the origin server, the response SHOULD be 201 (Created) and contain an entity which describes the status of the request and refers to the new resource, and a Location header (see section 14.30). and in section 14.30, For 201 (Created) responses, the Location is that of the new resource which was created by the request. Now suppose that my API allows batch creation of resources by

I am overriding Devise's failure response so that I can set a 401 status code. However, when the user fails to sign in, they are redirected to a page with a "you are being redirected" link. If I remove this :status => 401 from the redirect it works fine. class CustomFailure < Devise::FailureApp def redirect_url new_user_session_url(:subdomain => 'secure') end def respond if http_auth? http_auth else store_location! flash[:alert] = i18n_message unless flash[:notice] redirect_to redirect_url, :status => 401 end end end edit Alternatively I would like to display the flash message and remain on

In a jquery Ajax call I am currently handling statusCode of 200 and 304. But I also have "Error" defined" To catch any Errors that could come back. If there is a validation message related we return the status code of 400 - Bad Request. This then falls into the "Error" function before falling into the statusCode "400" function I had defined. Which means two actions happen. Ideally I would like to not define "Error" and "Success" and only define "statusCode" But what I need is to have a "Else" so that I don't need to declare every statusCode that exists only the 2-3 I want to handle differently

HTTP defines the status 401 Unauthorized for missing authentication, but this status only applies to HTTP authentication. What status should I return with a session cookie based system, when an unauthorized request happens? Formally, 403 Forbidden is the right response. It's defined as Authorization will not help and the request SHOULD NOT be repeated. The confusing part may be "Authorization will not help", but they really mean "HTTP authentication" (WWW-Authenticate) 403 I believe is technically correct (and probably most effective if you are implementing a custom API / protocol). 401 is not

I use HTTP status code symbols in code in a controller such as: render json: { auth_token: user.authentication_token, user: user }, status: :created or render json: { errors: ["Missing parameter."] }, success: false, status: :unprocessable_entity In the code of my request spec I also would like to use the symbols: post user_session_path, email: @user.email, password: @user.password expect(last_response.status).to eq(201) ... expect(last_response.status).to eq(422) However each test where I use the symbols instead of integers fails: Failure/Error: expect(last_response.status).to eq(:created)

Scenario: A POST request is sent to process an order that will result in data retrieval from an external datasource. There are three possible results: The datasource returned data for the request No data was available for the request (this is viewed as an error) The datasource couldn't be accessed (may be down for maintenance) An obvious response for 1 is 200: OK or 201: Created (an entity is created from this request). What status codes would be appropriate for 2 and 3 ? Status codes I have considered: 503: Service Unavailable when datasource is down 500: Internal Server Error when datasource