Re: [Cppcms-users] The role of cookie path

[Artyom B. <art...@gm...>]

> I am not sure if this helps..
>
> int main(int argc,char **argv){
>   ...
>   s.applications_pool().mount(cppcms::create_pool<normal_page>(),cppcms::mount_point(cppcms::mount_point::match_path_info,"^/(?:crud)/(\\d+)",1),cppcms::app::synchronous);
>
>   s.applications_pool().mount(cppcms::create_pool<download>(),cppcms::mount_point("/da/(.+)",1),cppcms::app::asynchronous);
> ...
> }
>

This is the clue.

The asynchronous application does not load session information by
default - because some session backends can be blocking and may lock
the entire event loop.
So in async app you first need to call session().load() and than use it.

Artyom

P.S.: Please open a feature request so to improve the behavior. I
noticed several times that it was causing issues for too many users