FogBugz Technical Support

A forum for technical support discussion related to Fogbugz.
The current FogBugz Knowledge Base can be found at

Posts by Fog Creek Employees are marked:

Release Notes
Network Status

Links containing [ or ] break

When a link contains [ or ], the automatic link detection stops at the character before, rendering those links broken (i.e. the do no longer point at the destination with all the intended information).

Example: http://server/page?param[]=bar

E.g. PHP supports that param[] syntax and browsers do not seem to automatically encode this somehow.
Markus Fischer Send private email
Tuesday, March 9, 2010
Seems the support software here is using the same algorithm, the links break the same way.
Markus Fischer Send private email
Tuesday, March 9, 2010
These characters are categorized as "unwise" by RFC2396, which lays out the specifications for URLs.

2.4.3. Excluded US-ASCII Characters

  Although they are disallowed within the URI syntax, we include here a description of those US-ASCII characters that have been excluded and the reasons for their exclusion.

  The control characters in the US-ASCII coded character set are not used within a URI, both because they are non-printable and because they are likely to be misinterpreted by some control mechanisms.

  control    = <US-ASCII coded characters 00-1F and 7F hexadecimal>

  The space character is excluded because significant spaces may disappear and insignificant spaces may be introduced when URI are transcribed or typeset or subjected to the treatment of word-processing programs.  Whitespace is also used to delimit URI in many contexts.

  space      = <US-ASCII coded character 20 hexadecimal>

  The angle-bracket "<" and ">" and double-quote (") characters are excluded because they are often used as the delimiters around URI in text documents and protocol fields.  The character "#" is excluded because it is used to delimit a URI from a fragment identifier in URI references (Section 4). The percent character "%" is excluded because it is used for the encoding of escaped characters.

  delims      = "<" | ">" | "#" | "%" | <">

  Other characters are excluded because gateways and other transport agents are known to sometimes modify such characters, or they are used as delimiters.

  unwise      = "{" | "}" | "|" | "\" | "^" | "[" | "]" | "`"

  Data corresponding to excluded characters must be escaped in order to be properly represented within a URI.
Rich Armstrong Send private email
Tuesday, March 9, 2010
Ok, lets see ..s o am I supposed to manually encode them to properly work?

It's not like I typed them manually (except in this example), but I simply literally copy them from the browser location bar (and it doesn't matter whether I copy it from IE or FF).

Your statements holds truth, no arguing, it's just doesn't seem to apply in the real world when working with URLs.

Markus Fischer Send private email
Wednesday, March 10, 2010
Sorry, reading my reply again, it sounded quite harsh, wasn't meant to be that. Just wanted to make my point I work with existing technologies and not trying to get something work I mashed up manually.

Markus Fischer Send private email
Wednesday, March 10, 2010
Did you write the app that uses the [] syntax in the URL?  Is it possible for you to encode those characters correctly?  The problem is that we can't change FogBugz to support those characters because the RFC says they aren't valid.
Michael H. Pryor Send private email
Wednesday, March 10, 2010
No, it's simply websvn. We tend to sometimes have the need to paste URLs into the cases as direct listed commits are not sufficient (e.g. diff review from commits to another branch, etc.)

I'm wondering what's going on with the RFC stuff when browsers will not encode this character in a special way within the URL at all ...

But hey, you're the Dev-Wizards and not me ;-) Thanks for your question though.
Markus Fischer Send private email
Wednesday, March 10, 2010
WebSVN is written in PHP though, so I think (if you desired) you could modify the source to encode them.
Michael H. Pryor Send private email
Thursday, March 11, 2010

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics
Powered by FogBugz Bug Tracking and Evidence-Based Scheduling.