`[New]` `RestServer` Plugin #3390

cschuchardt88 · 2024-07-02T18:58:38Z

Description

In this section you will learn about RestServer plugin and how it works.

Checkout the docs in ./docs/RestServer folder.

Dependencies

Microsoft.AspNetCore.JsonPatch.dll Required
Microsoft.AspNetCore.Mvc.NewtonsoftJson.dll Required
Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer.dll Required
Microsoft.AspNetCore.Mvc.Versioning.dll Required
Microsoft.OpenApi.dll Required
Newtonsoft.Json.Bson.dll Required
Newtonsoft.Json.dll Required
System.ServiceProcess.ServiceController.dll linux maybe
Microsoft.AspNetCore.Mvc.Versioning.dll Required
Microsoft.AspNetCore.Mvc.Versioning.dll Required
Microsoft.AspNetCore.Mvc.Versioning.dll Required
Microsoft.OpenApi.dll Swagger (optional)
Swashbuckle.AspNetCore.Swagger.dll Swagger (optional)
Swashbuckle.AspNetCore.SwaggerGen.dll Swagger (optional)
Swashbuckle.AspNetCore.SwaggerUI.dll Swagger (optional)
Swashbuckle.AspNetCore.Newtonsoft.dll Swagger (optional)
RestServer.xml Swagger UI (optional)

In Docker

RestServer
|   |   |-- Microsoft.AspNetCore.JsonPatch.dll
|   |   |-- Microsoft.AspNetCore.Mvc.NewtonsoftJson.dll
|   |   |-- Microsoft.AspNetCore.Mvc.Versioning.ApiExplorer.dll
|   |   |-- Microsoft.AspNetCore.Mvc.Versioning.dll
|   |   |-- Microsoft.OpenApi.dll
|   |   |-- Neo.ConsoleService.dll
|   |   |-- Newtonsoft.Json.Bson.dll
|   |   |-- Newtonsoft.Json.dll
|   |   |-- RestServer.deps.json
|   |   |-- RestServer.dll
|   |   |-- RestServer.pdb
|   |   |-- RestServer.xml
|   |   |-- Swashbuckle.AspNetCore.Newtonsoft.dll
|   |   |-- Swashbuckle.AspNetCore.Swagger.dll
|   |   |-- Swashbuckle.AspNetCore.SwaggerGen.dll
|   |   |-- Swashbuckle.AspNetCore.SwaggerUI.dll
|   |   |-- System.ServiceProcess.ServiceController.dll
|   |   |-- config.json
|   |   `-- runtimes
|   |       `-- win
|   |           `-- lib
|   |               `-- net6.0
|   |                   `-- System.ServiceProcess.ServiceController.dll

These files go in the same directory as the RestServer.dll. In neo-cli
plugins/RestServer/ folder.

Response Headers

Name	Value(s)	Description
server	neo-cli/3.6.0 RestServer/3.6.0	`neo-cli` and `RestServer` version.

JSON Serializer

RestServer uses custom Newtonsoft Json Converters to serialize controller action
responses and route parameters.

One Way Binding - Write only.

Neo.SmartContract.ContractState
Neo.SmartContract.NefFile
Neo.SmartContract.MethodToken
Neo.SmartContract.Native.TrimmedBlock
Neo.SmartContract.Manifest.ContractAbi
Neo.SmartContract.Manifest.ContractGroup
Neo.SmartContract.Manifest.ContractManifest
Neo.SmartContract.Manifest.ContractPermission
Neo.SmartContract.Manifest.ContractPermissionDescriptor
Neo.Network.P2P.Payloads.Block
Neo.Network.P2P.Payloads.Header
Neo.Network.P2P.Payloads.Signer
Neo.Network.P2P.Payloads.TransactionAttribute
Neo.Network.P2P.Payloads.Transaction
Neo.Network.P2P.Payloads.Witness

Two Way Binding - Read & Write

System.Guid
System.ReadOnlyMemory<T>
Neo.BigDecimal
Neo.UInt160
Neo.UInt256
Neo.Cryptography.ECC.ECPoint
Neo.VM.Types.Array
Neo.VM.Types.Boolean
Neo.VM.Types.Buffer
Neo.VM.Types.ByteString
Neo.VM.Types.Integer
Neo.VM.Types.InteropInterface
Neo.VM.Types.Null
Neo.VM.Types.Map
Neo.VM.Types.Pointer
Neo.VM.Types.StackItem
Neo.VM.Types.Struct

Remote Endpoints

Parametes {hash} can be any Neo N3 address or scripthash; {address} can be any Neo N3 address only; {number} and {index} can be any uint32.

Parameter Examples

{hash} - 0xef4073a0f2b305a38ec4050e4d3d28bc40ea63f5 or NiHURyS83nX2mpxtA7xq84cGxVbHojj5Wc
{address} - NiHURyS83nX2mpxtA7xq84cGxVbHojj5Wc
{number} - 1
{index} - 2500000

Paths

Utils
- [GET] /api/v1/utils/{hash}/address
- [GET] /api/v1/utils/{address}/scripthash
- [GET] /api/v1/utils/{hash}/{address}/validate
Node
- [GET] /api/v1/node/peers
- [GET] /api/v1/node/plugins
- [GET] /api/v1/node/settings
Ledger
- [GET] /api/v1/ledger/neo/accounts
- [GET] /api/v1/ledger/gas/accounts
- [GET] /api/v1/ledger/blocks?page={number}&size={number}
- [GET] /api/v1/ledger/blocks/height
- [GET] /api/v1/ledger/blocks/{index}
- [GET] /api/v1/ledger/blocks/{index}/header
- [GET] /api/v1/ledger/blocks/{index}/witness
- [GET] /api/v1/ledger/blocks/{index}/transactions?page={number}&size={number}
- [GET] /api/v1/ledger/transactions/{hash}
- [GET] /api/v1/ledger/transactions/{hash}/witnesses
- [GET] /api/v1/ledger/transactions/{hash}/signers
- [GET] /api/v1/ledger/transactions/{hash}/attributes
- [GET] /api/v1/ledger/memorypool?page={number}&size={number}
- [GET] /api/v1/ledger/memorypool/verified?page={number}&size={number}
- [GET] /api/v1/ledger/memorypool/unverified?page={number}&size={number}
- [GET] /api/v1/ledger/memorypool/count
Tokens
- [GET] /api/v1/tokens/balanceof/{address}
- NFTs
  - [GET] /api/v1/tokens/nep-11?page={number}&size={number}
  - [GET] /api/v1/tokens/nep-11/count
  - [GET] /api/v1/tokens/nep-11/{hash}/balanceof/{address}
- NEP-17
  - [GET] /api/v1/tokens/nep-17?page={number}&size={number}
  - [GET] /api/v1/tokens/nep-17/count
  - [GET] /api/v1/tokens/nep-17/{hash}/balanceof/{address}
Contracts
- [GET] /api/v1/contracts?page={number}&size={number}
- [GET] /api/v1/contracts/count
- [GET] /api/v1/contracts/{hash}
- [GET] /api/v1/contracts/{hash}/abi
- [GET] /api/v1/contracts/{hash}/manifest
- [GET] /api/v1/contracts/{hash}/nef
- [GET] /api/v1/contracts/{hash}/storage

Type of change

Optimization (the change is only an optimization)
Style (the change is only a code style for better maintenance or standard purpose)
Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
This change requires a documentation update

How Has This Been Tested?

By @superboyiii from neo-project/neo-modules#839

Checklist:

My code follows the style guidelines of this project
I have performed a self-review of my code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation
My changes generate no new warnings
I have added tests that prove my fix is effective or that my feature works
New and existing unit tests pass locally with my changes
Any dependent changes have been merged and published in downstream modules

src/Plugins/RestServer/Controllers/v1/ContractsController.cs

superboyiii · 2024-07-08T07:12:55Z

All contractstates are missing updatecounter in Contracts collections. Maybe need make result as contracts.ToJson().

superboyiii · 2024-07-08T10:38:53Z

src/Plugins/RestServer/Controllers/v1/ContractsController.cs

+                throw new QueryParameterNotFoundException(nameof(method));
+            try
+            {
+                var engine = ScriptHelper.InvokeMethod(_neosystem.Settings, _neosystem.StoreView, contracts.Hash, method, contractParameters, out var script);


Need supporting signer account and scope like what invokefunction did, or methods can't pass verifywitness.

src/Plugins/RestServer/Controllers/v1/LedgerController.cs

src/Plugins/RestServer/Controllers/v1/ContractsController.cs

src/Plugins/RestServer/Controllers/v1/LedgerController.cs

src/Plugins/RestServer/Controllers/v1/TokensController.cs

Jim8y · 2024-07-27T04:02:57Z

@cschuchardt88 conflict

superboyiii · 2024-08-08T08:48:43Z

result[0] of BalanceOf can be type of any.

@cschuchardt88

src/Plugins/RestServer/Tokens/NEP17Token.cs

shargon · 2025-02-10T11:17:19Z

Ban method should be by endPoint instead of controller before merge, some methods are prone to denial of service

cschuchardt88 · 2025-02-10T11:59:52Z

Maybe neo functions can be denied service. As for the webserver it won't be acceptable to an attack. However webserver calling neo functions, maybe...

Can you give a working example?

shargon · 2025-02-10T13:28:16Z

Can you give a working example?

ShowGasAccounts with one million accounts

cschuchardt88 · 2025-02-10T13:44:56Z

Nothing will happen to the server in that case. The page will just not load. The reason I didn't page it is, because I checked testnet and maintest and wasnt that many accounts that actually hold gas or neo. I believe the record gets deleted. I think until we have million records, we shouldn't worry about it.

A DOS happens when a server is manipulating data or killing a thread or process.

shargon

It must be secure, and now it is prone to denial of service.

cschuchardt88 · 2025-02-10T14:32:16Z

It must be secure, and now it is prone to denial of service.

It doesn't affect the node or the server at all. The request will timeout. If user stops the request this will just cancel the iterator. There is no different if the http server or cli ran the same function.

Timeout Settings

options.Limits.KeepAliveTimeout = TimeSpan.FromSeconds(_settings.KeepAliveTimeout); // default is 120 seconds in 'RestServer.json'
options.Limits.RequestHeadersTimeout = TimeSpan.FromSeconds(15);

I have done my R&D and this is why I added Timeout to the settings. So stuff like this can't proc.

shargon · 2025-02-10T23:37:14Z

It must be secure, and now it is prone to denial of service.

It doesn't affect the node or the server at all. The request will timeout. If user stops the request this will just cancel the iterator. There is no different if the http server or cli ran the same function.

Timeout Settings
options.Limits.KeepAliveTimeout = TimeSpan.FromSeconds(_settings.KeepAliveTimeout); // default is 120 seconds in 'RestServer.json'
options.Limits.RequestHeadersTimeout = TimeSpan.FromSeconds(15);
I have done my R&D and this is why I added Timeout to the settings. So stuff like this can't proc.

No, is not, the request can be canceled, but the iteration don't receive the cancelationRequest, so it will iterate until end, and another thread can do the same until denail the service.

cschuchardt88 · 2025-02-11T08:27:13Z

No, is not, the request can be canceled, but the iteration don't receive the cancelationRequest, so it will iterate until end, and another thread can do the same until denail the service.

Unless you have working example or evidence, http in dotnet doesn't work like this. It will cancel the thread that is running the iterator. There is no other thread that is running in the background or that was created for the iterator. It runs the thread where the request was executed. I recommend you do a little reading on kestrel about its life cycle. Now we can disable KeepAlive on that request that uses the iterator. So as soon as they disconnect it stops the thread.

Request draining with ASP.NET Core Kestrel web server

Kestrel tries to drain the request body. Draining the request body means reading and discarding the data without processing it.
Draining has a timeout of five seconds, which isn't configurable.
If all of the data specified by the Content-Length or Transfer-Encoding header hasn't been read before the timeout, the connection is closed.

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/request-draining?view=aspnetcore-9.0

dusmart · 2025-02-11T09:47:21Z

Can you give a working example?

ShowGasAccounts with one million accounts

Thank you for identifying this issue. This is indeed a significant DoS entry point. A simple request can consume considerable CPU and memory resources, especially given the current number of accounts.

Reference:

neo/src/Neo/Extensions/SmartContract/GasTokenExtensions.cs

Lines 23 to 40 in 292540e

    
           public static IEnumerable<(UInt160 Address, BigInteger Balance)> GetAccounts(this GasToken gasToken, DataCache snapshot) 
        
           { 
        
               if (gasToken is null) 
        
                   throw new ArgumentNullException(nameof(gasToken)); 
        
               if (snapshot is null) 
        
                   throw new ArgumentNullException(nameof(snapshot)); 
        
               var kb = new KeyBuilder(gasToken.Id, GasToken.Prefix_Account); 
        
               var prefixKey = kb.ToArray(); 
        
               foreach (var (key, value) in snapshot.Find(prefixKey, SeekDirection.Forward)) 
        
               { 
        
                   var keyBytes = key.ToArray(); 
        
                   var addressHash = new UInt160(keyBytes.AsSpan(prefixKey.Length)); 
        
                   yield return new(addressHash, value.GetInteroperable<AccountState>().Balance); 
        
               } 
        
           }

)

shargon · 2025-02-11T09:56:58Z

No, is not, the request can be canceled, but the iteration don't receive the cancelationRequest, so it will iterate until end, and another thread can do the same until denail the service.

Unless you have working example or evidence, http in dotnet doesn't work like this. It will cancel the thread that is running the iterator. There is no other thread that is running in the background or that was created for the iterator. It runs the thread where the request was executed. I recommend you do a little reading on kestrel about its life cycle. Now we can disable KeepAlive on that request that uses the iterator. So as soon as they disconnect it stops the thread.

Request draining with ASP.NET Core Kestrel web server

Kestrel tries to drain the request body. Draining the request body means reading and discarding the data without processing it.

Draining has a timeout of five seconds, which isn't configurable.

If all of the data specified by the Content-Length or Transfer-Encoding header hasn't been read before the timeout, the connection is closed.

https://learn.microsoft.com/en-us/aspnet/core/fundamentals/servers/kestrel/request-draining?view=aspnetcore-9.0

Trust in security experts, it will be better for you, this PR contains multiple Denial of Services end points.
I have not asked to delete them, just to secure them, I do not understand why that is a problem for you.

cschuchardt88 · 2025-02-11T10:01:12Z

Because your two's claims are built on assumptions. Mine are built on facts. see #3390 (comment)

If this is true then NativeContract.ListContracts is DOSable in RpcServer. Also thats goes for getting blocks with transactions if there are 10k transactions in a block in RpcServer.

dusmart · 2025-02-11T10:05:13Z

If this is true then NativeContract.ListContracts is DOSable in RpcServer. Also thats goes for getting blocks with transactions if there are 10k transactions in a block in RpcServer.

Thank you for pointing it out. Where is it in the RpcServer? The code is introduced in #3614.

cschuchardt88 · 2025-02-11T10:16:14Z

Thank you for pointing it out. Where is it in the RpcServer? The code is introduced in #3614.

neo/src/Plugins/RpcServer/RpcServer.Wallet.cs

Line 136 in 292540e

foreach (UInt160 account in wallet.GetAccounts().Select(p => p.ScriptHash))

neo/src/Plugins/RpcServer/RpcServer.Wallet.cs

Line 193 in 292540e

protected internal virtual JToken ListAddress(JArray _params)

dusmart · 2025-02-11T10:49:07Z

neo/src/Plugins/RpcServer/RpcServer.Wallet.cs

Line 136 in 292540e

foreach (UInt160 account in wallet.GetAccounts().Select(p => p.ScriptHash))

neo/src/Plugins/RpcServer/RpcServer.Wallet.cs

Line 193 in 292540e

protected internal virtual JToken ListAddress(JArray _params)

That’s not a major concern, as most wallets don’t contain many addresses. Additionally, openwallet is disabled by default in the RPCServer. However, in the current plugin, a simple curl http://127.0.0.1:10339/api/v1/ledger/gas/accounts request returns 7,929,779 characters in my test, which is a significant payload. I believe these two scenarios present different levels of risk. But in theory, you're right about it. It's better to protect it, either.

Because your two's claims are built on assumptions. Mine are built on facts. see #3390 (comment)

I feel disheartened by this response. I invested time and effort into conducting tests to help improve NEO's security, and it’s difficult for me to accept being dismissed this way. I truly appreciate productive discussions and differences in perspective, but let’s keep the focus on the PR itself and avoid making it personal.

Your expertise in the .NET field is undeniable, and I respect that. However, this doesn’t change the core issue—users can indeed place a significant load on a node with a simple request.

That said, I hadn’t initially noticed this problem, thanks to the good design in this plugin, such as the implementation of pagination and max size limits, which help mitigate many risks. ~~If we could adopt a similar approach here, it would be highly beneficial.~~ Also, credit to Shargon for originally identifying this issue.

It seems that pagination is quite challenging here (credit to @Hecate2). Shargon's proposal might be a better approach. It would be more efficient to give users control over banning high-load methods, and we should set that as the default.

shargon · 2025-02-11T11:09:48Z

Because your two's claims are built on assumptions. Mine are built on facts.

The fact is: if you put this plugin in a consensus node, I can deny the services and kill one consensus node, I told you how can this be more secure, and you refuse to do the changes.

If you want to delegate in kestrel the cancellation and you call your own code, you must listen HttpContext.RequestAborted, otherwise the task will wait until finish your code to be cancelled.

dusmart · 2025-02-11T12:08:13Z

To ensure my understanding was correct, I also consulted with security expert @vang1ong7ang on this issue. His view is that DoS risks should be assessed based on the theoretical worst-case scenario. For example, the worst-case for the NEO's account API could return 100 million records, while for the GAS's account API, it could return 100 million * 100 million records. From this perspective, it should fundamentally be considered as having a DoS risk.

Added shargon requests

cschuchardt88 · 2025-02-11T21:57:31Z

All you concerns have been addressed.

dusmart · 2025-02-12T06:09:53Z

Thanks for your new commit! You made a great point—while applying page and size pagination at the outer layer reduces the returned data, it doesn’t necessarily decrease the internal CPU and memory load if the underlying processing remains the same (credit to @Hecate2). We suspect that this pagination approach might not be as effective as expected. @shargon, what are your thoughts?

shargon · 2025-02-12T09:16:16Z

Thanks for your new commit! You made a great point—while applying page and size pagination at the outer layer reduces the returned data, it doesn’t necessarily decrease the internal CPU and memory load if the underlying processing remains the same (credit to @Hecate2). We suspect that this pagination approach might not be as effective as expected. @shargon, what are your thoughts?

I think that we also need to be able to disable some endPoints, do it by controller it could be not enough

cschuchardt88 · 2025-02-12T09:34:19Z

We could add this too rate-limiting : https://learn.microsoft.com/en-us/aspnet/core/performance/rate-limit?view=aspnetcore-9.0

Added RestServer Plugin

47e11e0

cschuchardt88 mentioned this pull request Jul 2, 2024

Create a 'getTransactions' RPC endpoint (plugin/extension) #3297

Open

cschuchardt88 added Waiting for Review Plugins labels Jul 4, 2024

Merge branch 'master' into add/plugins/rest-server

bd94807

superboyiii reviewed Jul 8, 2024

View reviewed changes

src/Plugins/RestServer/Controllers/v1/ContractsController.cs Outdated Show resolved Hide resolved

superboyiii reviewed Jul 8, 2024

View reviewed changes

superboyiii reviewed Jul 9, 2024

View reviewed changes

src/Plugins/RestServer/Controllers/v1/LedgerController.cs Outdated Show resolved Hide resolved

superboyiii reviewed Jul 9, 2024

View reviewed changes

src/Plugins/RestServer/Controllers/v1/ContractsController.cs Outdated Show resolved Hide resolved

Merge branch 'master' into add/plugins/rest-server

e261aa6

superboyiii reviewed Jul 10, 2024

View reviewed changes

src/Plugins/RestServer/Controllers/v1/LedgerController.cs Outdated Show resolved Hide resolved

superboyiii reviewed Jul 12, 2024

View reviewed changes

src/Plugins/RestServer/Controllers/v1/TokensController.cs Show resolved Hide resolved

cschuchardt88 and others added 6 commits July 16, 2024 11:58

Merge branch 'master' into add/plugins/rest-server

5e8d98f

Merge branch 'master' into add/plugins/rest-server

6ab87d5

Update neo.sln

a8ac960

Fixed issue with merging from master

03e2298

Added @superboyiii request changes PART-1

287bbd7

Merge branch 'master' into add/plugins/rest-server

08f74a6

Jim8y added the Need Update label Jul 27, 2024

cschuchardt88 and others added 7 commits July 27, 2024 17:06

Merge branch 'master' into add/plugins/rest-server

8f0c919

Update sln file

758894c

Added better checking for IsNep11Supported and IsNep17Supported

b45c59a

Added Confirmations to Block JSON output

9dd47d9

variable name fixes

b310d99

Merge branch 'master' into add/plugins/rest-server

bcf109d

Merge branch 'master' into add/plugins/rest-server

6d8f294

superboyiii reviewed Aug 8, 2024

View reviewed changes

src/Plugins/RestServer/Tokens/NEP17Token.cs Show resolved Hide resolved

shargon requested changes Feb 10, 2025

View reviewed changes

Merge branch 'master' into add/plugins/rest-server

974fbd6

Jim8y and others added 3 commits February 11, 2025 21:22

Merge branch 'master' into add/plugins/rest-server

2406ff8

Merge branch 'master' into add/plugins/rest-server

443d108

Added paging to neo and gas account endpoints\

f4400e7

Added shargon requests

cschuchardt88 dismissed Jim8y’s stale review via f4400e7 February 11, 2025 21:51

Jim8y and others added 2 commits February 12, 2025 16:45

Merge branch 'master' into add/plugins/rest-server

1baf2eb

Merge branch 'master' into add/plugins/rest-server

71fdbdf

Jim8y and others added 3 commits February 13, 2025 17:46

Merge branch 'master' into add/plugins/rest-server

b4f0659

Merge branch 'master' into add/plugins/rest-server

57f82cc

Merge branch 'master' into add/plugins/rest-server

422f6e1

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

`[New]` `RestServer` Plugin #3390

`[New]` `RestServer` Plugin #3390

cschuchardt88 commented Jul 2, 2024 •

edited

Loading

superboyiii commented Jul 8, 2024 •

edited

Loading

superboyiii Jul 8, 2024

cschuchardt88 Sep 1, 2024

Jim8y commented Jul 27, 2024

superboyiii commented Aug 8, 2024 •

edited

Loading

shargon commented Feb 10, 2025

cschuchardt88 commented Feb 10, 2025

shargon commented Feb 10, 2025

cschuchardt88 commented Feb 10, 2025 •

edited

Loading

shargon left a comment

cschuchardt88 commented Feb 10, 2025 •

edited

Loading

shargon commented Feb 10, 2025

Timeout Settings

cschuchardt88 commented Feb 11, 2025 •

edited

Loading

dusmart commented Feb 11, 2025

shargon commented Feb 11, 2025 •

edited

Loading

Request draining with ASP.NET Core Kestrel web server

cschuchardt88 commented Feb 11, 2025 •

edited

Loading

dusmart commented Feb 11, 2025

cschuchardt88 commented Feb 11, 2025

dusmart commented Feb 11, 2025 •

edited

Loading

shargon commented Feb 11, 2025

dusmart commented Feb 11, 2025

cschuchardt88 commented Feb 11, 2025

dusmart commented Feb 12, 2025

shargon commented Feb 12, 2025

cschuchardt88 commented Feb 12, 2025

[New] RestServer Plugin #3390

Are you sure you want to change the base?

[New] RestServer Plugin #3390

Conversation

cschuchardt88 commented Jul 2, 2024 • edited Loading

Description

Dependencies

In Docker

Response Headers

JSON Serializer

Remote Endpoints

Type of change

How Has This Been Tested?

Checklist:

superboyiii commented Jul 8, 2024 • edited Loading

superboyiii Jul 8, 2024

Choose a reason for hiding this comment

cschuchardt88 Sep 1, 2024

Choose a reason for hiding this comment

Jim8y commented Jul 27, 2024

superboyiii commented Aug 8, 2024 • edited Loading

shargon commented Feb 10, 2025

cschuchardt88 commented Feb 10, 2025

shargon commented Feb 10, 2025

cschuchardt88 commented Feb 10, 2025 • edited Loading

shargon left a comment

Choose a reason for hiding this comment

cschuchardt88 commented Feb 10, 2025 • edited Loading

Timeout Settings

shargon commented Feb 10, 2025

Timeout Settings

cschuchardt88 commented Feb 11, 2025 • edited Loading

Request draining with ASP.NET Core Kestrel web server

dusmart commented Feb 11, 2025

shargon commented Feb 11, 2025 • edited Loading

Request draining with ASP.NET Core Kestrel web server

cschuchardt88 commented Feb 11, 2025 • edited Loading

dusmart commented Feb 11, 2025

cschuchardt88 commented Feb 11, 2025

dusmart commented Feb 11, 2025 • edited Loading

shargon commented Feb 11, 2025

dusmart commented Feb 11, 2025

cschuchardt88 commented Feb 11, 2025

dusmart commented Feb 12, 2025

shargon commented Feb 12, 2025

cschuchardt88 commented Feb 12, 2025

`[New]` `RestServer` Plugin #3390

`[New]` `RestServer` Plugin #3390

cschuchardt88 commented Jul 2, 2024 •

edited

Loading

superboyiii commented Jul 8, 2024 •

edited

Loading

superboyiii commented Aug 8, 2024 •

edited

Loading

cschuchardt88 commented Feb 10, 2025 •

edited

Loading

cschuchardt88 commented Feb 10, 2025 •

edited

Loading

cschuchardt88 commented Feb 11, 2025 •

edited

Loading

shargon commented Feb 11, 2025 •

edited

Loading

cschuchardt88 commented Feb 11, 2025 •

edited

Loading

dusmart commented Feb 11, 2025 •

edited

Loading