Thunderhorse-Framework
diff --git a/‎lib/Thunderhorse.pm‎
Lines changed: 25 additions & 1 deletion b/‎lib/Thunderhorse.pm‎
Lines changed: 25 additions & 1 deletion
diff --git a/‎lib/Thunderhorse/Router/Location.pm‎
Lines changed: 11 additions & 2 deletions b/‎lib/Thunderhorse/Router/Location.pm‎
Lines changed: 11 additions & 2 deletions
diff --git a/‎t/router-actions.t‎
Lines changed: 10 additions & 2 deletions b/‎t/router-actions.t‎
Lines changed: 10 additions & 2 deletions
@@ -568,6 +568,20 @@ Action format is C<scope.method> where scope is one of C<http>, C<sse>, or
 C<websocket>, and method is an HTTP method for C<http> or C<sse> scope, or
 omitted for C<websocket>. Either part can be C<*> to match anything.
 
+If a C<.get> route is created, it is automatically valid for similar C<HEAD>
+requests as well. If special C<HEAD> handling is required, a check can be made
+in handler code:
+
+	sub handle ($self, $ctx)
+	{
+		...; # set headers
+
+		# return empty (but defined) response if we have HEAD, full body
+		# otherwise
+		return '' if $ctx->req->is_head;
+		return 'full body';
+	}
+
 Common action patterns:
 
 	# Match only HTTP POST requests
@@ -579,7 +593,7 @@ Common action patterns:
 	# Match only WebSocket connections
 	action => 'websocket'
 
-	# Match only Server-Sent GET Events
+	# Match only Server-Sent GET and HEAD Events
 	action => 'sse.get'
 
 	# Match any request type (default)
@@ -592,6 +606,16 @@ allowing different handlers for different request types:
 	$router->add('/api/data' => { to => 'post_data', action => 'http.post' });
 	$router->add('/api/data' => { to => 'stream_data', action => 'websocket' });
 
+If the handler is the same for all actions, it can be achieved with a simple
+for loop:
+
+	for my $action (qw(http.get http.post websocket)) {
+		$router->add('/api/data' => { to => 'handle_api_data', action => $action });
+	}
+
+Make sure that the order of route building is deterministic, and that C<name>
+(if provided) is unique.
+
 =head3 PAGI compatibility
 
 Thunderhorse was coded in such a way that allows it to fully integrate the PAGI
 
@@ -63,8 +63,17 @@ sub BUILD ($self, $)
 sub _build_action_re ($self)
 {
 	my ($scope, $method) = split /\./, $self->action;
-	$scope = $scope eq '*' ? qr{[^.]+} : quotemeta $scope;
-	$method = ($method // '*') eq '*' ? qr{(\.[^.]+)?} : quotemeta ".$method";
+	$scope = $scope eq '*' ? qr{[^.]+} : quotemeta lc $scope;
+
+	if (($method // '*') eq '*') {
+		$method = qr{(\.[^.]+)?};
+	}
+	elsif (lc $method eq 'get') {
+		$method = '[.](get|head)';
+	}
+	else {
+		$method = quotemeta lc ".$method";
+	}
 
 	return qr{^$scope$method$};
 }
 
@@ -58,7 +58,7 @@ package TestApp {
 		# Test multiple routes on same path with different actions
 		$router->add(
 			'/multi' => {
-				action => 'http.get',
+				action => 'HTTP.GET',
 			}
 		);
 
@@ -90,6 +90,11 @@ subtest 'should match exact scope and method' => sub {
 	is $no_match, undef, 'ws.get did not match';
 };
 
+subtest 'should match head with get' => sub {
+	my $match = _get_match($router, '/exact', 'http.head');
+	ok $match, 'route matched';
+};
+
 subtest 'should match wildcard method' => sub {
 	my $match = _get_match($router, '/wildcard-method', 'http.get');
 	ok $match, 'http.get matched';
@@ -156,7 +161,10 @@ subtest 'should match no action (matches anything)' => sub {
 
 subtest 'should match correct action on same path' => sub {
 	my $match = _get_match($router, '/multi', 'http.get');
-	is $match->location->action, 'http.get', 'http.get matched';
+	is $match->location->action, 'HTTP.GET', 'http.get matched';
+
+	$match = _get_match($router, '/multi', 'http.head');
+	is $match->location->action, 'HTTP.GET', 'http.head matched';
 
 	$match = _get_match($router, '/multi', 'http.post');
 	is $match->location->action, 'http.post', 'http.post matched';