[SOLVED]fpweb documentation do not cover middleware setup

[Sniper]

Hello y'all.
I haven't found how to create middleware using internal web server in this article https://wiki.freepascal.org/fpWeb_Tutorial.

Code: Pascal  [Select][+][-]

1. program webserver;
2.    
3. {$mode objfpc}{$H+}
4.  
5. uses
6. {$ifdef UNIX}
7.    cthreads, cmem,
8. {$endif}
9.    fphttpapp, httpdefs, httproute;
10.  
11. procedure route1(aReq: TRequest; aResp: TResponse);
12. begin
13.    aResp.content:='Hello, World!'
14. end;
15.  
16. begin
17.    HTTPRouter.registerRoute('/', @route1, true);
18.    Application.port := 8080;
19.    Application.threaded := true;
20.    Application.initialize;
21.    Application.run;
22.  end.
23.  

Could anyone point me where I can see any bits of this type of information?

[Leledumbo]

I haven't found how to create middleware using internal web server in this article https://wiki.freepascal.org/fpWeb_Tutorial.
...
Could anyone point me where I can see any bits of this type of information?

What kind of middleware do you expect? The tutorial doesn't cover any of the fpWeb components you get in Lazarus Component Palette on purpose, because... I simply don't know how to work with them. And while the previous router have some injectable events, the more recent httproute router is much simpler and is exactly how you code it: It only links URIs to procedures, everything else should be made on top of that.

[Sniper]

I haven't found how to create middleware using internal web server in this article https://wiki.freepascal.org/fpWeb_Tutorial.
...
Could anyone point me where I can see any bits of this type of information?

What kind of middleware do you expect? The tutorial doesn't cover any of the fpWeb components you get in Lazarus Component Palette on purpose, because... I simply don't know how to work with them. And while the previous router have some injectable events, the more recent httproute router is much simpler and is exactly how you code it: It only links URIs to procedures, everything else should be made on top of that.

"Middleware" I'm talking about is a function where I can check something in a query and the decide what to do next with it accept or decline fo example.
The ordinary modern request track looks like: "/route1" -> middleware1_function(write query log)->middlware2_function(check user credentials) -> route1_function
in pascal fpweb framework it might look like this HTTPRouter.RegisterRoute('/route1', @middleware1_function(@middleware2_function(@route1)));
the design patter for this type is decorator

[PierceNg]

"Middleware" I'm talking about is a function where I can check something in a query and the decide what to do next with it accept or decline fo example.
The ordinary modern request track looks like: "/route1" -> middleware1_function(write query log)->middlware2_function(check user credentials) -> route1_function
in pascal fpweb framework it might look like this HTTPRouter.RegisterRoute('/route1', @middleware1_function(@middleware2_function(@route1)));
the design patter for this type is decorator

These are called interceptors in fcl-web. Not in FPC 3.2.2, only in trunk. Here's trunk's demo. The relevant code:

Code: Pascal  [Select][+][-]

1. if Fauth<>'' then
2.     HTTPRouter.RegisterInterceptor('auth',@DoAuthorization);
3.   if not FQuiet then
4.     begin
5.     HTTPRouter.RegisterInterceptor('logstart',@DoRequestStart);
6.     HTTPRouter.RegisterInterceptor('logend',@DoRequestEnd,iaAfter);
7.     end;

[Leledumbo]

These are called interceptors in fcl-web. Not in FPC 3.2.2, only in trunk.

Ah, new feature that escapes my watch. I assume they will be executed in order of RegisterInterceptor call, yes?

[Sniper]

These are called interceptors in fcl-web. Not in FPC 3.2.2, only in trunk. Here's trunk's demo. The relevant code:

Code: Pascal  [Select][+][-]

1. if Fauth<>'' then
2.     HTTPRouter.RegisterInterceptor('auth',@DoAuthorization);
3.   if not FQuiet then
4.     begin
5.     HTTPRouter.RegisterInterceptor('logstart',@DoRequestStart);
6.     HTTPRouter.RegisterInterceptor('logend',@DoRequestEnd,iaAfter);
7.     end;

That is what I'm looking for. Thank you!

[PierceNg]

Ah, new feature that escapes my watch. I assume they will be executed in order of RegisterInterceptor call, yes?

Haven't looked thru the source. I am guessing for requests the interceptors are invoked first-added first-to-process, while for responses they are first-added last-to-process, typical of this middleware pattern.