HttpSessionFilter is not applied if using custom server:context-path

[michalpetrov]

Expected Behavior

Setting micronaut:server:context-path to any other value the / results in HttpSessionFilter not being applied hence session handling not working.

Not working:

micronaut:
  server:
    context-path: /foo
  session:
    http:
      cookie-path: /foo
      cookie: true

Workaround is by setting the filter regex-pattern:

micronaut:
  server:
    context-path: /foo
  session:
    http:
      cookie-path: /foo
      cookie: true
    filter:
      regex-pattern: /foo/.*

Actual Behaviour

No response

Steps To Reproduce

No response

Environment Information

No response

Example Application

No response

Version

4.9.2

[MahmudovaA]

We have the same problem with session handling when micronaut:server:context-path is configured.

In particular, a controller method with parameter Session responds with 400 Bad Request error with the message "Required argument [Session session] not specified".

@Controller("/demo")
public class DemoController {
    @Get
    public HttpResponse<?> getSession(Session session) {
        session.put("demo", "pippo);
        return HttpResponse.ok("pluto");
    }
}

This behaviour did not occur prior to version 4.8.x

Example Application
Demo micronaut session error

Version
4.9.4