Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Disable well-known #73

Open
lucabovo opened this issue Aug 24, 2022 · 4 comments
Open

Disable well-known #73

lucabovo opened this issue Aug 24, 2022 · 4 comments

Comments

@lucabovo
Copy link

lucabovo commented Aug 24, 2022

Hi all,
is there any option or configuration to disable the /.well-known path?

We need it for a public CoAP Server instance that we are running without authentication because of a limitation of field devices.

Thanks in advance for your help.

@lucabovo
Copy link
Author

lucabovo commented Nov 4, 2022

Hi @longshine @martindevans @SiMet @robreeves @delmet @billpratt,
any news about this request?

Please let me know, thank you.

@SiMet
Copy link
Contributor

SiMet commented Nov 5, 2022

I think you could create your own implementation of IServer. Please see CoapServer class and try to create your own.

I see that last commit was done 7 year ago.

@longshine
Copy link
Member

@lucabovo Hi there. Sorry for the late response. This repo is not actively maintained anymore.
As for your question, I suggest you could extend the CoapServer and customize it as you require.

For example, to remove .well-known you may have code like this:

class CoapServerWithoutWellknown : CoapServer
{
    public CoapServer(ICoapConfig config, params Int32[] ports)
            : base(config, ports)
    {
        Resource wellKnown = _root.GetChild(".well-known")
        _root.Remove(wellKnown)
    }
}

@lucabovo
Copy link
Author

@molinomatteo

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants