Tom Larkworthy

OK an explicit opt-in normalization filter seems to be safest choice.

Someone has had some weird interaction leading to 403 with sinatra before: https://serverfault.com/questions/690540/getting-403-forbidden-w-referer-on-nginxpassenger Seems close to the symptoms though not exactly the same. Pretty sure its this: https://stackoverflow.com/questions/10509774/sinatra-and-rack-protection-setting

If was gonna bank on a serverside oauth implementation these days its would be https://lucia-auth.com/

Also to use the binging API the module needs to be ESM I believe, so this issue is a blocker https://github.com/markusahlstrand/cloudworker-proxy/issues/133

You don't need to split the repository, but have the handlers imported with module syntax so the bundler can eliminate source code not used when deploying. It's quite burdensome looking...

Oh cool its alive. I updated the toolchain for node 18, I can merge all that back here if you want (I was jsut hacking so its not done that...

yeah before we get too ahead with features, we should remove the rotted dependancies and get onto idiomatic local modern cloudflare dev, including using the module export style of connecting...

WDYT? https://github.com/markusahlstrand/cloudworker-proxy/pull/120 Please advise me on your preferred ways-of-working if this PR is not how you would do it.

yeah I would rephrase this as give us access to the underlying runtime through "inbuilt" variable , you can build some seriously cool stuff and gives us the tools to...

Workaround https://observablehq.com/@endpointservices/example-custom-embed