go-chi/cors

Issues

• Allow customizable behavior on cors failure

  #30 opened a month ago by ablankz
  0

• Fixed error messages in TestDefault

  #28 opened a month ago by ablankz
  0

• AllowOriginFunc considered harmful (may lead to Web cache poisoning)

  #23 opened 10 months ago by jub0bs
  1

• Allowing methods that are not uppercase should be possible but isn't

  #27 opened 6 months ago by jub0bs
  1

• allow all origins wildcard not supported by chrome

  #17 opened 3 years ago by cameronbraid
  3

• Listing Origin as an allowed request header is unnecessary

  #26 opened 6 months ago by jub0bs
  0

• Document differences between upstream github.com/rs/cors and this fork

  #21 opened 2 years ago by VojtechVitek
  3

• Custom header with undercore is been normilize to a header without it

  #14 opened 2 years ago by ocalvet
  4

• Handler: Actual request If no Origin present allows the call to complete without validating the origin.

  #10 opened 4 years ago by ahamansh
  2

• Preflight OPTIONS request should respond with StatusNoContent(204) and not StatusOK(200)

  #1 opened 4 years ago by jeevankk
  2

• IE11 Internet Explorer 11 does not add the Origin header on a CORS request across sites of a trusted zone.

  #11 opened 5 years ago by jqdurham
  1

• CORS isn't work

  #8 opened 5 years ago by grtfou
  1

• License

  #3 opened 6 years ago by explodingcamera
  12