You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
All endpoints seem to support url parameters, x-www-form-urlencoded, json, and headers. Would it be better security to limit the formats allowed for the requests? If so, is there an easy way to do that now?
classAuthenticationTest < ActionDispatch::IntegrationTestsetupdo@user=create(:user)@sign_in_url='/auth/sign_in'enddescribe'sign in'dotest'with email and password x-www-form-urlencoded'dopost@sign_in_url,params: {email: @user.email,password: @user.password}assert_equal200,statusendtest'with email and password headers'dopost@sign_in_url,headers: {email: @user.email,password: @user.password}assert_equal200,statusendtest'with email and password url params'dopost"#{@sign_in_url}?email=#{@user.email}&password=#{@user.password}"assert_equal200,statusendtest'with email and password json'dopost@sign_in_url,as: :json,params: {email: @user.email,password: @user.password}assert_equal200,statusendendend
Thanks!
The text was updated successfully, but these errors were encountered:
andrewferk
changed the title
Limit formats allowed to use make requests
Limit formats allowed to make requests
Sep 17, 2016
In an effort to cleanup this project and prioritize a bit, we're marking issues that haven't had any activity in a while with a "close-in-7-days" label. If we don't hear from you in about a week, we'll be closing this issue. Obviously feel free to re-open it at any time if it's the right time or this was done in error!
If you are still having the issue (especially if it's a bug report) please refer to our new Issue Template to provide some more details to help us solve it.
All endpoints seem to support url parameters, x-www-form-urlencoded, json, and headers. Would it be better security to limit the formats allowed for the requests? If so, is there an easy way to do that now?
Thanks!
The text was updated successfully, but these errors were encountered: