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
<cfifstructKeyExists(_taffyRequest.headers, "origin") AND (application._taffy.settings.allowCrossDomaineqtrueorlen(application._taffy.settings.allowCrossDomain) gt0)>
When running an API that had only some resources available for CORS setting the global allowCrossDomain = false caused Access-Control-Allow-Headers to be output twice as i was sorting the cors like the below.
Presumably the line of code in the api.cfc is set up to check the length of allowCrossDomain as you can put in a list of domains, but with false also being treated as a string it also then passes this check.
Its not a huge issues and the workaround was to set allowCrossDomain to an empty string - Running taffy 3.1.
CF 2016 / Taffy 3.1 / Java 15.0.1
Taffy/core/api.cfc
Line 249 in 3cefedf
When running an API that had only some resources available for CORS setting the global
allowCrossDomain = false
causedAccess-Control-Allow-Headers
to be output twice as i was sorting the cors like the below.Presumably the line of code in the api.cfc is set up to check the length of
allowCrossDomain
as you can put in a list of domains, but withfalse
also being treated as a string it also then passes this check.Its not a huge issues and the workaround was to set
allowCrossDomain
to an empty string - Running taffy 3.1.The text was updated successfully, but these errors were encountered: