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
I configured the application's defaultMime to be json. The customSerializer.cfc is configured with getAsJson as default, but it doesn't seem to be working
Chromium appears to be using the following as the request Accept header rather than something generic like "/". (I'm testing using Microsoft EdgeDev with a work profile.)
I've updated core.buildRequestArguments() to check for overloading of the Accept header to return defaultMime when both text/html and image/ are used so that the configured default mime works.
Is this a good approach? I don't believe that explicit API requests for XML will use an Accept header that includes both text/html and image/, but I could be wrong.
The text was updated successfully, but these errors were encountered:
I configured the application's
defaultMime
to bejson
. The customSerializer.cfc is configured withgetAsJson
as default, but it doesn't seem to be workingChromium appears to be using the following as the request Accept header rather than something generic like "/". (I'm testing using Microsoft EdgeDev with a work profile.)
text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Firefox 125.0.1 uses the following Accept header:
text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,*/*;q=0.8
I've updated core.buildRequestArguments() to check for overloading of the Accept header to return
defaultMime
when bothtext/html
andimage/
are used so that the configured default mime works.Is this a good approach? I don't believe that explicit API requests for XML will use an Accept header that includes both
text/html
andimage/
, but I could be wrong.The text was updated successfully, but these errors were encountered: