|
|
| Reporter | AltaDeSaxa | Assigned To | Ommina | |
|---|
| Priority | normal | Severity | minor | Reproducibility | always |
|---|
| Status | resolved | Resolution | fixed | |
|---|
|
|
| Summary | 0001962: "505 ILLEGAL INPUT OR ACCESS DENIED" when groupname includes correctly-escaped ampersand |
|---|
| Description | When trying to look up the group "&" over the UDP API, my client sends the following command:
GROUP s=<session>&tag=t2&gname=&
Here the "&" is encoded correctly as specified in the UDP API Definition. However, the server replies with "505 ILLEGAL INPUT OR ACCESS DENIED".
|
|---|
| Steps To Reproduce | Look up the group "&" over the UDP API, with the "&" encoded as "&" |
|---|
| Additional Information | I am not sure if this is limited to the GROUP command. The length of the name does not seem to be the cause, as "a" looks up just fine. |
|---|
| Tags | No tags attached. |
|---|
|
|
