Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [orion-dev] Question marks in resource name

Hi Mike,

I believe we should be accepting all such characters in file names, and we have fixed a few bugs similar to this recently. Please open a bug report for the specific cases you are hitting and we will investigate. Be sure to describe either steps to reproduce in the orion client UI, or what exact HTTP requests you are sending to the server if it is a custom UI. Encoding problems can occur on both client and server side so it is important to know how you are hitting these. I suspect it many cases it is a simple encoding problem and we'll be able to get them addressed quickly.


From:        Mike Kucera/Toronto/IBM@IBMCA
To:        orion-dev@xxxxxxxxxxx,
Date:        09/26/2013 03:59 PM
Subject:        [orion-dev] Question marks in resource name
Sent by:        orion-dev-bounces@xxxxxxxxxxx


I am working with the IBM RD Traveler team. We are using Orion as part of a web-based development environment for IBM mainframes. I'm here to ask for help with an issue we are having.

We can't open the editor on files where the name contains special characters. Characters like * ? $ @ and # are all legal on the mainframe. When we generate links for these files we URL-encode these characters. However Orion still does not seem to be handling them properly.

I'm noticing two issues.

If a name ends with '?' or '#' it gets removed in the request for the file contents. Its common for the mainframe to generate datasets with names like this: MKUCERA.JOB00310.D0000103.?
My guess is that Orion is interpreting the question mark as the start of query parameters. We encode the ? as %3F so it should not do that.

None of the special characters are URL-encoded in the request for the file contents. I'm not exactly sure what's the correct thing to do here, but ? at lest should be re-encoded because our server is interpreting that as the start of query parameters.

Am I doing something wrong or is Orion not able to handle these special characters?


Mike Kucera
Rational Developer for AIX and Linux
IBM Toronto Lab

orion-dev mailing list

Back to the top