You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The idea is to allow the same worker to service multiple domains ("zones"). Through Worker Routes, there's no reason why you can't/shouldn't be able to do this in a real application.
And with SSL for SaaS, this may be way more common.
add hostname to request data
add App.host('example.com').add('GET', '/foo', handler) API
The text was updated successfully, but these errors were encountered:
Should also maybe allow host() to accept a pattern?
App.host(':service.example.com').get('/greet/:name',(req,res)=>{const{ service, name }=req.params;res.end(`hello ${name}, you are on the ${service} portal!`);});
Should also maybe allow host() to accept a pattern?
App.host(':service.example.com').get('/greet/:name',(req,res)=>{const{ service, name }=req.params;res.end(`hello ${name}, you are on the ${service} portal!`);});
This would be great for enterprise zones, which can proxy wildcards.
The idea is to allow the same worker to service multiple domains ("zones"). Through Worker Routes, there's no reason why you can't/shouldn't be able to do this in a real application.
And with SSL for SaaS, this may be way more common.
hostname
to request dataApp.host('example.com').add('GET', '/foo', handler)
APIThe text was updated successfully, but these errors were encountered: