Missing AsyncURIMatcher::iExact method

[JanPetterMG]

Platform

ESP32

IDE / Tooling

pioarduino

What happened?

Wanted to migrate to the new AsyncURIMatcher, but there's no iExact method, even though it's listed as an example here. My IDE can't find it, and looking at the source code, it looks like it doesn't exists.

Side note, exact seems like the only real alternative, but there was no examples of how to apply flags. After some debugging I found an example tucked away in a comment in the source code here: AsyncURIMatcher::CaseInsensitive. Would be easier if there was an enum like AsyncURIMatcher::flags::CaseInsensitive or similar, because the argument takes an uint16_t without hinting about supported values.

Stack Trace

class "AsyncURIMatcher" has no member "iExact"

Minimal Reproductible Example (MRE)

Try following the examples here, specifically this line: server.on(AsyncURIMatcher::iExact("/case"), handler);

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).

[coderabbitai[bot]]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Related Issues

• Build error on ESP32S3 #355
• ESPAsyncWebServer.h:1107:49: error: passing 'const AsyncServer' as 'this' argument discards qualifiers [-fpermissive] #194
• ESPAsyncWebServer Library Compatibility Issues with ESP32-S3 and ESP-IDF #260
• Error parsing HTTP POST parameters bug in srv/WebRequest.cpp (with text/plain content-type) #279
• Failed to compile simple project having ESPAsyncWebServer #207

👤 Suggested Assignees

• jrr
• stef-ladefense
• ayhamalji2
• igorfi
• trycoon

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord or schedule a call!

[JanPetterMG]

Quick follow up question, what's the difference between prefix and dir? The documentation linked previously is quite long, but doesn't really get to the point. They seem identical, with the exception of a trailing / that's automatically gets added if it's "forgotten" by the developer.

Would like to use dir to match content in a single directory, but it seems to function equal to prefix, which obviously matches contents in subdirectories too. Then there's also this ext method for file extension matching, but it seemingly won't match anything if there's no file extension even if I don't specify any (/directory/ or even /directory/*). I don't want to be rude, but these matching methods seems counter intuitive. Hoping it's just a bunch of bugs.

[mathieucarbou]

@JanPetterMG : please have a look at the code like you did and also the examples in the project.

The real doc is the code itself.
This is hard and time consuming to maintain the doc so we do what we can.

If you do really like doc more than reading code, I would suggest you open a PR and contribute to help this OSS project.

Thanks!

[mathieucarbou]

@JanPetterMG : I've just pushed an updated version (done by AI and quickly reviewed)

[JanPetterMG]

Seemingly, since you didn't read my post before closing the issue, why should I care and read the code (1600 lines), when the release notes instead points me directly to that documentation link instead?

The code snippet I referred to, is still there, in the exact same place as I linked it to in the issue. Nothing has changed!

ESPAsyncWebServer/examples/URIMatcher/README.md

Line 203 in 26f4552

server.on(AsyncURIMatcher::iExact("/case"), handler);

[JanPetterMG]

Closing this, as it's not an discussion, but rather a bug report with a follow up question!

[mathieucarbou]

That is not a bug report as we define them.
Your follow up question is also not a bug report.

[JanPetterMG]

Discussions doesn't need upstream code changes, still there was 2 commits. It might not have been a formal bug report, but it certainly was an issue, or else why were those commits necessary in the first place?

This is just silly!

[mathieucarbou]

Discussions doesn't need upstream code

That's not true : they often lead to code change

but it certainly was an issue

Some doc needed an update, indeed, but that's not what we call an issue. That's also not up to you to decide what is and is not considered an issue in this org and the way things are handled.

You report was more a support ticket with a remark about some non update doc plus a support question, that you could have answered your self if you had the will to look at the example.

This is just silly!

Yes indeed.

And I encourage you to also read the wiki and go over all the things you consider to be an issue to fix them.

Would be better to help and contribute than be insulting over the team that is maintaining these OSS projects on their spare time.

[JanPetterMG]

That's not true : they often lead to code change

Depends on how you define it, but from my experience, it rarely happens in majority of public repositories on GitHub. In private repositories, yes, but there's usually other unwritten rules and higher levels of formality when the public isn't involved.

Some doc needed an update, indeed, but that's not what we call an issue. That's also not up to you to decide what is and is not considered an issue in this org and the way things are handled.

The world isn't black and white, typos in documentation are unwanted bugs as well, maybe not enough to call it an issue, but referencing non-existent code in public documentation, is to me an issue that should be fixed. Critical? No, but it's still issues worth fixing.

You report was more a support ticket with a remark about some non update doc plus a support question, that you could have answered your self if you had the will to look at the example.

Did you forget what I was referencing? Example code, and examples doesn't solve anything when they are simply wrong.

This is just silly!

Yes indeed.

Having this conversation in the first place is indeed very silly.

And I encourage you to also read the wiki and go over all the things you consider to be an issue to fix them.

Sorry, but I'm not a developer, I try to fix as many things as possible, and in this case I even asked about the intentions because it looked like an oversight. It's impossible to fix a piece of code, if you don't know what it's supposed to do in the first place. Even the documentation was unclear about this.

Would be better to help and contribute than be insulting over the team that is maintaining these OSS projects on their spare time.

Sorry, not to be rude, but you pushed a commit and commented it was no longer an issue, without even taking a look at the specific code I was referring to. As a result another commit was pushed, but all this wouldn't happen in the first place if someone actually read what I wrote, instead of just skimming and assuming.

Sorry for being a regular human, and not an developer at your superior skill level. /s

Over and out!