Hello! I have found that the root of the problem I am describing is the method how the ActiveRecord migrator detects the migrations that need to be run. The problem surfaces only in more complex systems, and can be more easily imagined to arise with rails, but it is independent from rails and might arise with gems as well. Suppose the following scenario: Two rails applications, sharing a database,
Hi, We've recently been investigating reports from our users that they are unable to submit forms. Upon investigation it appears that browsers can get in a state where Rail's CSRF (Cross-Site Request Forgery) protection stops the form being submitted. To reproduce It's possible to produce a minimal Rails app which has this problem: How to replicate it on mobile Safari (tested on iOS9): Load a page
リリース、障害情報などのサービスのお知らせ
最新の人気エントリーの配信
処理を実行中です
j次のブックマーク
k前のブックマーク
lあとで読む
eコメント一覧を開く
oページを開く