This page has three main sections. (Note that the listings could be empty.) moreā€¦ Tip: Remember the back-button! And don't click the number on the left.

  1. The first item displays a term, URL, text or picture.
  2. Followed by a (still unordered) listing of statements about this subject. (for details follow ">"-link)
  3. Separated by a horizontal rule a "reverse" listing of statements referring to this item in object position.

The great uncertainty HTTP's use brings resulted in broken redirects again. (After many years working.)

The Issue

When OID's are referenced in user/browser-visible URL's their location is embedded into the URL. Browsers are redirected to what is understood to be the canonical representation of the URL string. (Whatever canonical means. Well: it's at least supposed to be valid according to the standards.)

However to be practically usable, we spent time to make sure it works with widely used browsers. Especially we made sure those would not re-encode the URL and re-request using a different encoding. This happend to be the case for years. With firefox beeing used as the reference in case of doubt.

At some point mozilla seems to have decided it's time to change. So things do not always work anymore.

The Result

Sorry but: There are situations resulting in an endless redirect loop.

We will take on this, but it might take a long time. This is outright considered a low-priority issue. URL-redirects are rarely required. And browsers should not do such re-encoding in the first place. We are not here to work around the browsers bugs. Sorry for the rant.

do we need this link?
4087 created > 2015-10-16 13:58:24 +0200
4088 creator (registered) > jfw

27 comment