Pode fails to respond

[slick789]

Describe the Bug

Using one of the examples on GitHub, Pode fails to respond after 5 clicks on between home page and in succession using 'Use-PodeWebTemplates' Putting the webpage in DevTools you can observe a blocking behaviour on the favicon (static) etc.

Steps To Reproduce

Steps to reproduce the behavior:

1. http://localhost:8090/
2. Click in fairly quick succession between the 2 pages in the sidebar
3. Observe on the 6th click that Pode takes ages to return

Expected Behavior

Should be able to accept more than 5 clicks in quick succession.

Screenshots

If applicable, add screenshots to help explain your problem.

Platform

• OS: Windows
• Browser: Edge, Chrome (Firefox seems more tolerant but still has the problem)
• Versions:
  • Pode: v2.11.1 (latest public release)
  • PowerShell: v1.0.0r2 (latest pre-release)

[Badgerati]

Hi @slick789, are you able to say which example you were testing with - or give the code for it?

Under the version for PowerShell you've put "1.0.0r2" - I'm assuming this is the Pode.Web version?

[slick789]

Hi @Badgerati, apologies for the delay in responding as I have been sidetracked. The sample I was testing out was https://github.com/Badgerati/Pode.Web/tree/develop/examples/login-azure-ad.ps1. Absolutely love the simplicity of Pode and AD integration which works well, but the fact that clicking between the pages rapidly causes issues means I can’t really demo it to my management team. Sorry you are spot on with the Pode.Web version in the Powershell field. It bug seems consistent in PS7.0 to 7.5. Would really appreciate this being fixed as I would like push my team down the Use-PodeWebTemplate route as it means my team doesn’t need to write html.

[breento]

I have the same problem, with every type of pode.web usage. It doesn't matter if you use authentication or not. A few pages load fine and then the 5th or 6th page let the server hang for around 30 seconds. With pode.web 1.0.0r2 and Powershell 7.4.7

[slick789]

Hi @Badgerati, have you been able to replicate the bug? It’s stopping me from rolling out a few solutions now. If it can’t be fixed then I need to identify a similar product, but would prefer to use Pode as it’s a its great for me apart from this bug.

[breento]

Interesting, with Pode.Web 0.8.3 I can't reproduce the issue, but with 1.0.0r1 or 1.0.0r2 I can always reproduce the issue.

[slick789]

You are spot on @breento it seems to have been broken in r1 and r2. I have it working now using 0.8.3, thanks for the head’s up. Hopefully it will be resolved.

[breento]

Hey @slick789 I found a "workaround" in https://github.com/Badgerati/Pode.web/issues/660 If you add -ResponseType Http to Use-PodeWebTemplates the issue is somehow fixed. The rest of the server seems to still work over https but I don't know what the ResponseType Http really does.

@Badgerati Do you know if this will be fixed?

[Badgerati]

Hey @breento @slick789,

-ResponseType Http will work for most people as expected - I'm tempted to make it the default in v1.0 and it'll act the same as v0.8. -ResponseType SSE is still HTTP, but it enables async callbacks between the server and client - enabling you to update elements during long running processes without waiting for the whole "button click logic" to finish.

The issue is with SSE, and I'm actually working on fixing as I type this 😄 it's a large fix, and will cover a lot of tickets for SSE and WebSockets in Pode and Pode.Web.