tinyhttp VS router

After this I really hit the ball rolling and was able to find more issues to work on. One thing that I enjoyed was that all of my PRs were drastically different from each other. I worked on correcting documentation for AdonisJS, fixed a HTTP Content-Type Header bug in tiny-http, and then finally even created a short script for users to load up their own local version of the Electron documentation site.

I worked on Issue 360. Essentially, when a user would set the "Content-Type" header before returning the file, the framework would overwrite the "previous" header, with the type that it determined from the files type.

tinyhttp: a modern web framework written in TypeScript. It uses tsm in its documentation examples as a simple way to get users up and running quickly

The framework I decided to use today was tinyhttp, with an API similar to Express, I don't have a specific reason to use this framework and the example code is easily replicated to other frameworks.

Oak is a middleware framework for Deno’s native HTTP server and Deno Deploy. It is influenced by Koa (hence the anagram) and includes a middleware router inspired by @koa/router.

The cookie part is crucial, but the CORS really depends on the implementation on bank.com. When sending an AJAX request to another domain, browsers first send a pre-flight OPTION request, to check the CORS rules on the destination domain. Only if the CORS works out will the browser send the "real" request. If bank.com implements a proper OPTION endpoint on /transfer that doesn't start any transfers, but just returns the CORS headers, the "real" transfer won't be called. It payes off to be redundant with security, so having both of these is good. If you're using Koa, koa-router has allowed methods to easily expose an OPTIONS endpoint for all other existing endpoints.