Brian Walendzinski
Brian Walendzinski
I've added v1.0 types to DefinitelyTyped. `npm install -D @types/pulsar-client`
@rkaw92 You can submit a pull request to the definitely typings repo if you find anything outdated and it'll get merged.
My workaround for now. ```python async def example_guard(connection: ASGIConnection, _: BaseRouteHandler) -> None: if connection.scope.get("method") == "OPTIONS": return # guard logic ```
> > My workaround for now. > > ```python > > async def example_guard(connection: ASGIConnection, _: BaseRouteHandler) -> None: > > if connection.scope.get("method") == "OPTIONS": > > return > >...
> It would be easy enough to bypass calling guards for OPTIONS requests - my question is, should it only apply to the options handlers that we generate, or should...
> My issue with excluding generated `OPTION` handlers by default is: What if you _want_ to include guards for them? IMO all security related things should be strict by default...
Makes VirtioFS practically unusable and actually negatively impacts the host machine after some time.