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
In latest version, variable-templating breaks in URL of the operation template. Reason for this is the use of url.resolve that causes variable-template string "{variable}" to get parsed into URL format and internally loopback-connector-rest uses string match to determine if variable-template is being used.
Reverted the fix in PR#10
The text was updated successfully, but these errors were encountered:
We can possibly use decodeURI V8 method to do URI decoding. Check for all characters is done as follows using REPL
> var b = url.resolve('https://abc.com/','/abc~a!b@c$d*e(f)?a=b\\c&b={de},f^g;`k|j+"de"&c=\'<a>\'#fragment')
undefined
> b
'https://abc.com/abc~a!b@c$d*e(f)?a=b%5Cc&b=%7Bde%7D,f%5Eg;%60k%7Cj+%22de%22&c=%27%3Ca%3E%27#fragment'
> decodeURI(b)
'https://abc.com/abc~a!b@c$d*e(f)?a=b\\c&b={de},f^g;`k|j+"de"&c=\'<a>\'#fragment'
In latest version, variable-templating breaks in URL of the operation template. Reason for this is the use of url.resolve that causes variable-template string "{variable}" to get parsed into URL format and internally loopback-connector-rest uses string match to determine if variable-template is being used.
Reverted the fix in PR#10
The text was updated successfully, but these errors were encountered: