ActionController::RoutingError: No route matches [CONNECT] "/"

[Torsten Rüger]

Hi,

i've been getting the subject error for some while in production. 

I've tried to find out what that connect even means with little avail. 

But i was generally surprised how much hacking attempts are being made, so i'm pretty sure it's ill intent.

Just, i can't seems to get rid of the error. I tried to add rescue_from to my ApplicationController, as in:

  rescue_from ActionController::RoutingError, with: :error_404

but that doesn't do it. The call goes from phusion through rack and rails, and ends in 

actionpack-4.2.5/lib/action_dispatch/middleware/debug_exceptions.rb:21:in `call'

Has anyone encountered this in the wild ?

Torsten

[Frederick Cheung]

On Tuesday, December 29, 2015 at 6:13:52 PM UTC, Torsten Rüger wrote:
> Hi,
>
>
> i've been getting the subject error for some while in production. 
> I've tried to find out what that connect even means with little avail. 
> But i was generally surprised how much hacking attempts are being made, so i'm pretty sure it's ill intent.

CONNECT is an http method used for proxies to allow tunnelling arbitrary traffic through a proxy: basically someone has been scanning for misconfigured proxies (and probably other stuff too). Just a fact of life really.

>
>
> Just, i can't seems to get rid of the error. I tried to add rescue_from to my ApplicationController, as in:
>
>
>
>   rescue_from ActionController::RoutingError, with: :error_404
>
>

This type of routing error can't be rescued like that since rails doesn't know which controller should be used. If it bothers you then you could try blocking it at the webserver level (eg https://httpd.apache.org/docs/2.4/mod/core.html#limit)

Fred

[Torsten Rüger]

Thanks Fred,

strange to think there should be an error that can't be handled in rails. Still, thanks for the answer, which i am unfortunately not sure i understand.

Are you saying i should have  a

<Limit CONNECT>

</Limit>

[Frederick Cheung]

On Wednesday, December 30, 2015 at 9:25:01 PM UTC, Torsten Rüger wrote:
> Thanks Fred,
>
>
> strange to think there should be an error that can't be handled in rails. Still, thanks for the answer, which i am unfortunately not sure i understand.

You could also handle via a rack middleware or by supplying a custom exception app (see http://guides.rubyonrails.org/configuring.html#rails-general-configuration)

>
>
> Are you saying i should have  a
> <Limit CONNECT>
>
>
> </Limit>
>

Not sure - never done this, but this seems to be the mechanism Apache provides for filtering requests based on http method.

Fred