爲什麼我的rails站點收到一個OPTIONS請求錯誤，它不包含任何跨域請求？

Question

我的Rails應用程序，和關閉，遇到致命錯誤：

ActionController::RoutingError (No route matches [OPTIONS] "/"): 

一些google搜索後，我發現這是關係到跨域請求，並使用CORS域之間進行通信。該應用程序沒有任何內置的請求。這個錯誤是否意味着某方正在嘗試聯繫來自另一個域的我的域根？還是我錯過了明顯的東西？

完整的錯誤：

F, [2016-09-29T21:38:56.500387 #28585] FATAL -- : 
ActionController::RoutingError (No route matches [OPTIONS] "/"): 
    actionpack (4.2.5.1) lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call' 
    actionpack (4.2.5.1) lib/action_dispatch/middleware/show_exceptions.rb:30:in `call' 
    railties (4.2.5.1) lib/rails/rack/logger.rb:38:in `call_app' 
    railties (4.2.5.1) lib/rails/rack/logger.rb:20:in `block in call' 
    activesupport (4.2.5.1) lib/active_support/tagged_logging.rb:68:in `block in tagged' 
    activesupport (4.2.5.1) lib/active_support/tagged_logging.rb:26:in `tagged' 
    activesupport (4.2.5.1) lib/active_support/tagged_logging.rb:68:in `tagged' 
    railties (4.2.5.1) lib/rails/rack/logger.rb:20:in `call' 
    actionpack (4.2.5.1) lib/action_dispatch/middleware/request_id.rb:21:in `call' 
    rack (1.6.4) lib/rack/methodoverride.rb:22:in `call' 
    rack (1.6.4) lib/rack/runtime.rb:18:in `call' 
    activesupport (4.2.5.1) lib/active_support/cache/strategy/local_cache_middleware.rb:28:in `call' 
    rack (1.6.4) lib/rack/sendfile.rb:113:in `call' 
    actionpack (4.2.5.1) lib/action_dispatch/middleware/ssl.rb:24:in `call' 
    railties (4.2.5.1) lib/rails/engine.rb:518:in `call' 
    railties (4.2.5.1) lib/rails/application.rb:165:in `call' 
    passenger (4.0.60) lib/phusion_passenger/rack/thread_handler_extension.rb:74:in `process_request' 
    passenger (4.0.60) lib/phusion_passenger/request_handler/thread_handler.rb:141:in `accept_and_process_next_request' 
    passenger (4.0.60) lib/phusion_passenger/request_handler/thread_handler.rb:109:in `main_loop' 
    passenger (4.0.60) lib/phusion_passenger/request_handler.rb:455:in `block (3 levels) in start_threads' 

Answer 1

事實證明，服務器CPU剛剛擠破頭，我們升級到一個更大的。我們的新理論是，當CPU過載時，負載平衡器會在服務器之間交換用戶，並且這似乎是一個跨域請求。不管這是否真的是這樣，這個問題就消失了。