fixed dead links
This commit is contained in:
@@ -29,7 +29,7 @@ You can extend the `RequestHandler` class to create custom handlers that process
|
|||||||
Because `RequestHandler` is an abstract class, you need to implement both the `handle()` method and the `super` constructor in your custom handler to define the logic that should be executed
|
Because `RequestHandler` is an abstract class, you need to implement both the `handle()` method and the `super` constructor in your custom handler to define the logic that should be executed
|
||||||
when a request is received.
|
when a request is received.
|
||||||
|
|
||||||
Since `RequestHandler` is an abstract class, you can leverage and chain HDI's to create cleaner and more maintainable route logic (more on that in the [Handler Default Implementations](/flash/handler-default-implementations) section).
|
Since `RequestHandler` is an abstract class, you can leverage and chain HDI's to create cleaner and more maintainable route logic (more on that in the [Handler Default Implementations](/flash/advanced/handler-default-implementations) section).
|
||||||
|
|
||||||
### 2. SimpleHandler
|
### 2. SimpleHandler
|
||||||
|
|
||||||
|
|||||||
@@ -13,7 +13,7 @@ corresponding file from the server. This is where a dynamic file server comes in
|
|||||||
|
|
||||||
::: warning
|
::: warning
|
||||||
The dynamic file server relies heavily on the concept of dynamic handlers, which are handlers that will resolve for
|
The dynamic file server relies heavily on the concept of dynamic handlers, which are handlers that will resolve for
|
||||||
any subpath of the endpoint they are registered to (see [Handler Types](/flash/handlers) for more info).
|
any subpath of the endpoint they are registered to (see [Handler Types](/flash/core-concepts/handlers) for more info).
|
||||||
:::
|
:::
|
||||||
|
|
||||||
## Usage
|
## Usage
|
||||||
|
|||||||
Reference in New Issue
Block a user