Problem with registering complex paths

[ikorman]

Platform

ESP32

IDE / Tooling

PlatformIO

What happened?

For some reason I have issue when registering pages that have complex paths, like for example "/config/ResetConfig" where handleResetConfig never gets triggered. Here is sample code for registration:

` server.on("/config", HTTP_GET, [this](AsyncWebServerRequest *request)
{ this->handleConfig(request); });

server.on("/config", HTTP_POST, [this](AsyncWebServerRequest *request)
          { this->handleConfig(request); });

server.on("/config/ResetConfig", HTTP_GET, [this](AsyncWebServerRequest *request)
          { this->handleResetConfig(request); });

server.on("/configResetDevice", HTTP_GET, [this](AsyncWebServerRequest *request)`

In above example, when I direct my browser to "/config/ResetConfig" nothing happens, but when rename path in the code to "/configResetConfig" handler is called when accessing "/configResetConfig". What is causing this?

Stack Trace

n/a

Minimal Reproductible Example (MRE)

` server.on("/config", HTTP_GET, [this](AsyncWebServerRequest *request)
{ this->handleConfig(request); });

server.on("/config", HTTP_POST, [this](AsyncWebServerRequest *request)
          { this->handleConfig(request); });

server.on("/config/ResetConfig", HTTP_GET, [this](AsyncWebServerRequest *request)
          { this->handleResetConfig(request); });

server.on("/configResetDevice", HTTP_GET, [this](AsyncWebServerRequest *request)`

I confirm that:

• I have read the documentation.
• I have searched for similar discussions.
• I have searched for similar issues.
• I have looked at the examples.
• I have upgraded to the lasted version of ESPAsyncWebServer (and AsyncTCP for ESP32).

[mathieucarbou]

Hello @ikorman ,

For some reason I have issue when registering pages

Please not that you having an issue does not necessary mean there is a bug in the library that warrants a bug report ;-)
But report are for bugs in the library only.
Please read carefully the issue template and use support discussions next time. Thanks!

In your case, just make sure that the most specific handler are registered before the more generic.
Ordering is important because this is how overriding routes also work.

Register for example /config/ResetConfig before /config

That's it ;-)

[ikorman]

You are write, I apologize, it's a bit a late, so i completely forgot about discussion section

Regarding your solution, it's spot on, it works like a charm :) Thx for the great work you have put into this library 👍