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
Seems like there is an inconsistency between the :ring/request spec and the servlet implementation, in particular the map created by build-request-map. This is based on my assumption that the request handed to my handler from ring jetty server, for example, should satisfy the :ring/request spec.
The spec says the :query-string key is optional but the value must be a string? and the implementation returns the :query-string key always but sometimes a null (nil) value via the .getQueryString method.
The text was updated successfully, but these errors were encountered:
Seems like there is an inconsistency between the
:ring/request
spec and the servlet implementation, in particular the map created bybuild-request-map
. This is based on my assumption that the request handed to my handler from ring jetty server, for example, should satisfy the:ring/request
spec.The spec says the
:query-string
key is optional but the value must be astring?
and the implementation returns the:query-string
key always but sometimes a null (nil
) value via the.getQueryString
method.The text was updated successfully, but these errors were encountered: