It's all about the answers!

Ask a question

Enough reasons to submit an RFE for removing or modifying the URL double encoding from an Eclipse client, 4.0.3 and higher ?

long TRUONG (3654117146) | asked Jul 23 '15, 8:58 p.m.
 As per jazz forum post 177137, our external customers RTC access from Eclipse client is blocked by our TMG. which blocks double encoded URLs. 

IBM introduced URI double encoding into 4.0.3 Eclipse client to resolve Defect 251859.

We are thinking of submitting an RFE to either remove or modify this double encoding, based on below reasons. Would appreciate your thoughts on keeping the encoding or on jumping on the band wagon with us, if an RFE is submitted.

Does IBM need to turn to URL double encoding, increasing security risk:
    • to deal with "Error: Invalid URI encountered when uri contains user with a space in their login name (as an approver)"
    • which only happens in limited circumstances; instead of just either disallow blank in  login name or offer a different fix which is of limited scope and affecting less of other normal use of the RTC.
    • And if there are enough customers running into the issues in the defect, a special version of the Eclipse client can be offered without affecting the general body of users.
    • Also, why it has to be full URL double encoding when the URL only needs to go through a second pass of encoding only unencoded blanks.

One answer

permanent link
Donald Nong (14.5k414) | answered Jul 28 '15, 5:16 a.m.
I would say just ahead and submit it. Give as much background information as possible. The development team will evaluate it and give you a response.

long TRUONG commented Jul 28 '15, 12:56 p.m.

 Thanks Donald. Will be submitting one.

Your answer

Register or to post your answer.