Actions
Bug #6281
closed
? escaped in in the path variable parameter of ncf-builder URL
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
0
Name check:
Fix check:
Regression:
Description
Sometimes '?' are rewritten "%3F" in ncf-builder, preventing parsing of path parameter.
Updated by Vincent MEMBRÉ almost 10 years ago
- Description updated (diff)
- Status changed from New to Pending technical review
- Assignee changed from Vincent MEMBRÉ to François ARMAND
- Pull Request set to https://github.com/Normation/ncf/pull/172
Updated by François ARMAND over 9 years ago
- Subject changed from rewrite wrong url preventing access to path variable to ? escaped in in the path variable parameter of ncf-builder URL
- Description updated (diff)
- Status changed from Pending technical review to Rejected
So,
The problem seems to only appears when we try to use "#?!xxxxx" kind of parameter for an (old) version of ncf-builder that is expecting only "?xxxx". Something with angularjs, but we didn't find quite excatly what.
And in fact, we don't care, because for old version of ncf-builder, we don't want to have unescaped "?" in the fragment part of the url.
So rejecting it, with "oh, the computer are doing the right stuff, sorry digital master lords"
Updated by Alexis Mousset over 2 years ago
- Target version changed from 0.x to ncf-0.x
- Priority set to 0
Updated by Alexis Mousset over 2 years ago
- Project changed from 41 to Rudder
- Category set to Generic methods
Actions