-
Notifications
You must be signed in to change notification settings - Fork 209
Issues: PerlDancer/Dancer
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
cookie "plack_session" set twice when using session "PSGI"
#1227
opened Oct 24, 2020 by
nicolasfranck
Failed test 'No XXE SSRF vulnerability in our XML handling' (Dancer-1.3514_02)
#1221
opened Oct 4, 2020 by
eserte
Is it possible to return a Dancer::Response that is left unchanged?
#1211
opened Mar 16, 2020 by
nicolasfranck
May accidentally match a route if %+ was already populated
Bug
#1187
opened Jun 13, 2018 by
bigpresh
request->uri_base contains dispatch.(f)cgi when Dancer is executed via DirectoryIndex (Apache 2.4)
#1171
opened Oct 16, 2017 by
isync
core - serializer - JSON is needed and is not installed at /usr/share/perl5/Dancer/Serializer.pm line 33.
#1170
opened Sep 29, 2017 by
aaronsuns
Dancer::Request returns 500 on Content-Type: multipart/form-data with no boundary
#1167
opened Apr 21, 2017 by
rkgjohn
Use of YAML.pm to read config is hard-coded (so YAML::XS is not used even when specified)
#1163
opened Oct 11, 2016 by
1nickt
megasplat inconsistent with multiple slashes (
//
) in (or ending) path
#1158
opened Apr 12, 2016 by
veryrusty
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.