Skip to content

Add fdi-version header to requests #2

@rishabhpoddar

Description

@rishabhpoddar

Frontend SDKs must

  • API requests have a fdi-version header for versioning purposes. The format is a X.Y,X1.Y1... for example 1.2,3.4,1.1. In the driver, we must take care to remove spaces and then get the latest common version between the two SDKs (like we do for CDI)

Drivers must:

  • Extracting the latest, common (between frontend and backend SDK) FDI version from the request and passing that to the module. If no FDI is present, then assume the latest FDI supported by the backend SDK. If FDI is present, but none matching, then throw an appropriate error.
  • This also needs to be exposed in Access-Control-Allow-Headers
  • If it is missing, we assume the latest version supported by the driver.

  • supertokens-website
  • supertokens-auth-react
  • ios
  • android
  • react native
  • nodejs
  • javalin
  • flask
  • fastapi
  • golang
  • laravel

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions