Project

General

Profile

Actions
Copy link

Bug #1256

closed

setInternalPath URI encoding

Added by Anonymous over 12 years ago. Updated almost 12 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Wim Dumon
Target version:
3.3.0
Start date:
04/25/2012
Due date:
% Done:

0%

Estimated time:

Description

The function escapes some valid URL characters in its parameter string making it difficult to use component delimiters.

For example, the search string 'http://localhost/search/param1+param2' will be converted to 'http://localhost/search/param1%2bparam2'.

Actions
Copy link
 #1

Updated by Koen Deforche over 12 years ago

  • Status changed from New to InProgress
  • Assignee set to Wim Dumon
  • Target version set to 3.2.2

This would be a regression, wim can you find out when and why this happened ?

Actions
Copy link
 #2

Updated by Koen Deforche over 12 years ago

  • Target version changed from 3.2.2 to 3.2.3
Actions
Copy link
 #3

Updated by Kurt Roeckx about 12 years ago

Any update on this?

Actions
Copy link
 #4

Updated by Koen Deforche about 12 years ago

  • Target version changed from 3.2.3 to 3.3.0
Actions
Copy link
 #5

Updated by Wim Dumon almost 12 years ago

  • Status changed from InProgress to Resolved

Hi Kurt,

I took a look at this and we currently only seem to escape the necessary characters from the URL: %, , ' ', # and &. I'm afraid that without these, we may have problems to convert an URL unambiguously when it is entered in the address bar by the user. '', being an alternative for '%20', is problematic to decode unambiguous in our 'ugly' implementation of the internal paths (when your wt application is deployed on '/', with the query string encoded path).

BR,

Wim.

Actions
Copy link
 #6

Updated by Koen Deforche almost 12 years ago

  • Status changed from Resolved to Closed
Actions
Copy link

Also available in: Atom PDF