Comments (8)
Interesting, I will try to reproduce and see.
Since we have specific connector for cgi, libfcgi, ... we may be able to do something.
if PATH_INFO always comes decoded from the variables, then we could set the WSF_REQUEST.percent_encoded_path_info accordingly.
from ewf.
How?
On 13 May 2014 07:57, Jocelyn Fiat [email protected] wrote:
Interesting, I will try to reproduce and see.
Since we have specific connector for cgi, libfcgi, ... we may be able to
do something.
if PATH_INFO always comes decoded from the variables, then we could set
the WSF_REQUEST.percent_encoded_path_info accordingly.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/130#issuecomment-42923129
.
from ewf.
SCRIPT_NAME is also defined to not be URL-encoded, so where is the
information to come from?
On 13 May 2014 08:02, Colin Adams [email protected] wrote:
How?
On 13 May 2014 07:57, Jocelyn Fiat [email protected] wrote:
Interesting, I will try to reproduce and see.
Since we have specific connector for cgi, libfcgi, ... we may be able to
do something.
if PATH_INFO always comes decoded from the variables, then we could set
the WSF_REQUEST.percent_encoded_path_info accordingly.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/130#issuecomment-42923129
.
from ewf.
At the moment, I am getting round the problem because I know (at least, I
hope I do) that the URLs I am using do not contain any special characters,
such as / - so i can take the path_info, and reconstruct the encoded
version.
But soon I will have to deal with objects whose name includes a /
character. At which point I can no longer tell if the / in the path_info is
a path-separator or a data character that was originally percent-encoded.
On 13 May 2014 08:43, Colin Adams [email protected] wrote:
SCRIPT_NAME is also defined to not be URL-encoded, so where is the
information to come from?On 13 May 2014 08:02, Colin Adams [email protected] wrote:
How?
On 13 May 2014 07:57, Jocelyn Fiat [email protected] wrote:
Interesting, I will try to reproduce and see.
Since we have specific connector for cgi, libfcgi, ... we may be able to
do something.
if PATH_INFO always comes decoded from the variables, then we could set
the WSF_REQUEST.percent_encoded_path_info accordingly.—
Reply to this email directly or view it on GitHubhttps://github.com//issues/130#issuecomment-42923129
.
from ewf.
I did a few tests on a ubuntu machine, running apache2
and I get those output
https://gist.github.com/jocelyn/e46ad4f39b808ea87d14
so we have a few things to double check..
from ewf.
The pull request #136
address those issues.
This is not yet merged, so don't hesitate to comment.
from ewf.
Is this pull request merged yet?
from ewf.
No, I was worry about not getting any comment.
But I will merge it before end of November if no-one disapprove it.
from ewf.
Related Issues (20)
- WebSocket Client HOT 1
- WebSocket Test HOT 1
- / as part of the value of a URI template variable results in handler not being found HOT 6
- WSF_REQUEST.save_uploaded_file: unsafe
- WSF_POST_HELPER does not support non-RESTful POSTs HOT 2
- gewf and autodetect which connector to use
- Consistency of Not Modified responses in WSF_METHOD_HELPER HOT 1
- Policy-driven framework should reject PUT requests that contain a Content-Range header HOT 1
- Add a last_modified routine to WSF_SKELETON_HANDLER HOT 1
- WSF_TRACE_RESPONSE does not include Content-Type header HOT 1
- Possible replacement for code 301 Moved permanently
- Use of 411 Length required response code HOT 2
- CORS headers for policy-driven framework HOT 2
- VARY header set to application/json rather than accept HOT 1
- Documentation error in {WSF_SKELETON_HANDLER}.check_request
- WSF_REQUEST.cookies_table does not terminate on cookies without a value. HOT 2
- Issues are WSF_RESPONSE.status_code/status_is_set
- Segmentation Fault on map_uri_template_agent_with_request_methods HOT 4
- JSON_PARSER.parse_string can exhaust memory HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from ewf.