Developer forum

Forum » Dynamicweb 10 » Custom endpoints not registered in DW 10.9.1

Custom endpoints not registered in DW 10.9.1

E-mail notifications
Mikkel Hammer
Mikkel Hammer
Reply
Posted on 11/11/2024 11:43:16

Hi DW,

The setup i mention in this other post https://doc.dynamicweb.com/forum?PID=1605&ThreadID=94855 has stopped working in DW 10.9.1, but is working in DW 10.8.0.

There no error logs in the Dynamicweb solution, but with the help of my colleague Kevin (the hardcode MVP saviour), we found these logs in the EventViewer of the environment.

and this log message is logged on DW startup, which i guess is related to the issue

Have you changed anything regarding the setup for addins and HTTPS?

Our development and test environments are not running HTTPS.

 

The endpoints just startet returning 500 error message, but as i mentioned earlier - they produced no error logs in the Dynamicweb Administration, only in the EventViewer for the PC.

Which is kind of concerning aswell.

 

You can test it yourself here: Dynamicweb Headless Delivery API

 

Hope you can help :)

Best regards,

Mikkel Hammer


Replies

 
Mikkel Hammer
Mikkel Hammer
Posted on 11/11/2024 11:57:37
Reply

I also tried adding logging myself, which were not hit either 

 

 
Mikkel Hammer
Mikkel Hammer
Posted on 13/11/2024 11:16:00
Reply

Hi DW,

Just a extra note, it also works on 10.8.7 - so im guessing something has changed in the setup from 10.8.x to 10.9.x.

It also doesnt seem to be related to https, since our test environment has it setup.

Hope it helps :)

 

Best regards,

Mikkel Hammer

 
Jeppe Eriksson Agger Dynamicweb Employee
Jeppe Eriksson Agger
Posted on 13/11/2024 13:00:40
Reply

Hi Mikkel,

I've looked into this and while I haven't isolated the issue I do have some observations.

  • Using http or https doesn't make a difference
  • Everything works if the assembly is loaded from the bin folder rather than from Files
  • All current versions of 10.8.X are unaffected
  • All current version of 10.9.X are affected

It could potentially be related to some recent changes to our handling of Dependency Injection which resulted in minor changes in the order that certain types are registered and loaded. I'm still looking into it as I haven't found the exact cause yet. You can follow the issue with bug #22062.

- Jeppe

 
Mikkel Hammer
Mikkel Hammer
Posted on 13/11/2024 13:57:47
Reply

Thanks Jeppe, looking forward to what you find!

I'll follow along on the issue

 

Best regards,

Mikkel Hammer

 

You must be logged in to post in the forum