Alias directive case-sensitive?

I've come across an issue with the Alias directive... I set an alias in the ServerAdmin and realized that upon saving it converted everthing in the target path to lowercase.
The directive subsequently did not work. When I edit the path manually via the shell to be uppercased, the directive works fine.
My filesystem (per Disk Utility) is HFS Journaled, bot NOT case sensitive. So what gives? Is this a bug in the WebAdmin (shouldn't really convert to lowercase, should it?) or a bug in mod_alias? Or am I missing something alltogether?
Powebook G4 Mac OS X (10.4.3)

I do not know of a fix but I have implemented a work around.
1. Quit Server Admin as you are about to edit the config files by hand.
2. Open terminal and go to the sites directory containing the config files. Apologies for not being more specific, but it's been a while since I have had to edit these files and I am no longer dealing with a server.
3. Open the desired site conf file in your choice of editor. You will probably need to sudo to gain privileges to save the changes.
4. Find the section that contains all the aliases. I think this is the <IfModule mod_alias.c> section. Take note of the format of the aliases.
5. Add an Include directive (http://httpd.apache.org/docs/1.3/mod/core.html#include) to include a file that you will create in a few steps. This file will contain aliases defined by hand. For example, if my web site was website.com I might call the file website_aliases.conf.
6. Save your edits and quit editing the file.
7. Create the file you referenced in the include directive and place your aliases in there. Example line from website_aliases.conf: Alias /image /ftp/pub/image
Check and make sure the privileges on the new file match the privileges of the other conf files.
Server Admin will not bother the include directive and will not touch any entries in the extra file referenced in the include directive. Server Admin will also not be aware of any of the aliases in the extra file referenced. This means that all aliases containing upper case letters must be manually entered.
Caution: My description is purposely vague in places because messing with config files by hand can get you into trouble if you are not careful. (Or I simply forgot to mention something My advice would be to use apachectl configtest to check your changes before you attempt to soft restart the web server. If you have made a mistake, the web server will fail to restart.
As far as restarting the web server after making changes to any apache config file, you can either use apachectl from the command line or simply open Server Admin, select the web server service, and toggle an option. This will cause the save button to be enabled and cause apache to soft restart and reread it's configuration.

Similar Messages

Mod_osso.conf - sso protected - case sensitive URL not working

Greetings,
I have modified my mod_osso.conf (see below) file to protect the following URL "http://host.domain.com:7777/test".
If you enter the above URL - you are properly challenged for a user-name and password. HOWEVER, if you enter "http://host.domain.com:7777/TEST" or any other variation /Test, /tEst, /teSt etc. SSO does not get enabled.
I'm missing something, what is it???
Thanks,
Bill G...
mod_osso.conf file
LoadModule osso_module modules/ApacheModuleOSSO.DLL
<IfModule mod_osso.c>
OssoIpCheck on
OssoIdleTimeout off
OssoConfigFile D:\oracle\903_j2ee\Apache\Apache\conf\osso\osso.conf
# BG ADD
<Location /test>
AuthType Basic
Require valid-user
</Location>
</IfModule>

If you are on a UNIX-based server, URLs are always case-sensitive.
Enter an directive for every possible combination, or create the alias/redirect for each combination in the httpd.conf (recommended)
HTH
LLB

How to retrieve column names in a query in a case sensitive way

Given a query, I want to extract all the column names/aliases in the query in a case-sensitive way.
When I use dbms_sql.describe_columns() or java.sql.ResultSetMetaData classes getColumnName() or getColumnLabel()
it returns the columns name ONLY in Upper case.
My application needs to extract the column names in the same case as it appears in the query string.
Is there any API to get this without parsing the SQL query string?
Thanks
PS: The dbms_sql.describe_columns() returns the column name in upper case.
declare
IS
l_column_recs DBMS_SQL.DESC_TAB;
l_cur NUMBER;
l_column_count NUMBER;
BEGIN
l_cur := dbms_sql.open_cursor;
dbms_sql.parse(l_cur, 'select target_type from targets', dbms_sql.NATIVE);
dbms_sql.describe_columns(l_cur, l_column_count, l_column_recs);
FOR i IN l_column_recs.FIRST..l_column_recs.LAST
LOOP
dbms_output.put_line(l_column_recs(i).col_name);
end loop;
end;
/

As far as the result set is concerned, though, the column name is in all upper case. If you query the data dictionary, you would see that the TARGET_TYPE column in the TARGETS table is stored in upper case.
The way Oracle works is that column names that are not enclosed in double-quotes are converted to upper case in the data dictionary and elsewhere and then Oracle looks for the column name in the table definition. That is what allows Oracle to have case-insensitive identifiers unless a user specifies case-sensitive identifiers by enclosing the identifier in double quotes.
If you changed the query to be
SELECT target_type as "target_type"
FROM targetsOracle should report the alias in a case sensitive fashion because you've now indicated that the alias should be treated as case sensitive.
Justin

Time Machine Case-Sensitive Error

I've read several posts about people who encounter the Time Machine error that arises when TM thinks that one of the volumes (source or destination) is case-sensitive while the other is not. Some people encounter this error genuinely, by which I mean that there is in fact a discrepancy between the file systems; this is not the situation I wish to address.
There are other people - myself included - who have been using TM successfully for months or longer until one day the error crops up. When we check Disk Utility, both source and destination are shown to be case-insensitive. Many approaches have been suggested, from rebooting to reformatting, and many people have reported success; however, it appears to me that the problem has not been solved, since the cause of the problem has not been identified.
In my own experience rebooting sometimes fixes the problems temporarily (for a few weeks) before it later reappears. But I would rather not reboot repeatedly, repeatedly Verify the disks using Disk Utility (finding no errors every time), or reformat unless I am sure that it will fix the problem once and for all. With that in mind, does anyone know of a permanent fix to this problem?
Details:
- TM thinks that the source volume Macintosh HD is case-sensitive
- Disk Utility says that both the source and the external Firewire destination are case-insensitive

Hi, and welcome to the forums.
I've not seen any such posts here (and I read at least the title of every post in both the Leopard and Snow Leopard Time Machine forums).
There are problems, on occasion, when there's a case-sensitive disk image of some kind on the internal HD (some downloaded software comes on case-sensitive disk images, for some reason); but that doesn't seem to be what you're experiencing.
What, exactly, does the message say?
There might be some sort of problem with your internal HD. When this happens, does the disk show it's S.M.A.R.T. status as Verified? Does +Verify Disk+ ever show an error?
I'd be inclined to try a "full reset" per #A4 in the Time Machine - Troubleshooting *User Tip,* also at the top of this forum. It's possible the preference file that directs you to is corrupted. This is a long shot, of course, but worth a try.
If this happens again, look for any disk images, and try to get the exact message. You may also want to look in your system.log for messages.

Business Partner search (case sensitive)

I create a Business Partner with the following details
FirstName - Vikram
LastName - Chandna
When i search the created Business Partner via Tcode-FPP3 by name, the
search is case In-Sensitive(i.e Font case doesn't matter)
But, when i search the same in the Database table-BUT000 directly or in
the SAP Query/Reports , the search is Case-Sensitive.
Why?
Thanks & Regards,
Gagan

Hi Gagan,
The field BU_SORT1 in Table BUT000 which is for search option has data type as Character without Lowercase.If the Lowercase option (in the output characteristicks) is ticked in the table, the sytem will allow you to search based on Lowercase as well.
Regards
Amitav

Case sensitive table names and column names in 8i or 9i databases

Hi everybody,
I've got a couple of business-side colleagues who insist that Oracle table and column names are case sensitive. That is, there is a setting in the set up of a database that lets you pick if table and column names are case sensitive. For example, this would mean that there could be a table named EMP in a given schema schema plus a table named emp in that same schema.
Can this be true? I'd be surprised of course, but I've been surprised before.
Thanks for any direction.
-- Bill Loggins

You can do it, but I would avoid it like the plague.
SQL> create table "a" (b date);
Table created.
SQL> create table "A" (b date);
Table created.
I think I would refuse to work on a database where this has been used !

BUG - FTP with case sensitive server

My provider uses case sensitive file and directory names. I
created a directory 'OtherStuff' on the server directly (not from
remote view). In Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'. When I created a default html file
and PUT it, FTP failed to find the directory but continued and put
the default html file in the root, overwriting my default web file.
Yes, I erred. However, it would be good if Dreamweaver would
stop when it encounters a cd failure.

jjstafford wrote:
> My provider uses case sensitive file and directory
names. I created a
> directory 'OtherStuff' on the server directly (not from
remote view). In
> Dreamweaver's FTP setup I erred by specifying the
subdirectory of 'otherstuff'.
> When I created a default html file and PUT it, FTP
failed to find the
> directory but continued and put the default html file in
the root, overwriting
> my default web file.
>
> Yes, I erred. However, it would be good if Dreamweaver
would stop when it
> encounters a cd failure.
>
>
You can enable case sensitive link checking in the site
manager.
However, this is more the issue of the OS, rather then DW.
Windows -
which is the OS you use, I assume - is about the only OS
(that I know
of) which is case insensitive!
All Linux/Unix based servers are case sensitive.

How to convert case-sensitive to extended journal format

I have two apple computers (extended journal format) that have been backed up via a time capsule. I have just noticed that the TC is formatted as case-sensitive. I do not know why case-sensitive. In an effort to ensure consistency of file format then I seek to somehow remove case-sensitive formatting. I presume no/minimal underlying case-sensitivity issues within file names as source data is not formatted in case-sensitive manner.
I have tried SuperDuper to clone the TC to an external HDD but the application cloned the formatting in addition to the data.
I have attempted use of Disk Utility to copy content from source (TC) to destination (HDD) but this yielded error messages that noted different file format types.
It there a way to convert/remove case sensitive formatting from TC?
I appreciate that I could simply reformat TC to extended journal format but this would presumably erase all my backup data.
Any guidance most welcomed.

RossM wrote:
So I guess my choice is to "leave well alone" as Pondini suggests and accept the fact that cloning TC onto HDD has now formatted my new HDD as case-sensititive.
Actually, you may have two choices, depending on how you're going to be backing-up to the new HD:
Your best bet, by far, is to back up to it directly, rather than connecting it to the TC. That's much faster and more reliable. If so:
* Leave the TC backups alone. Reformat the HD as case-ignorant and let Time Machine start fresh on it. You can always see and restore from the old ones via the Browse... option, per Time Machine - Frequently Asked Question #17.
* Format the HD as case-sensitive and copy the backups from the TC to it. But don't copy the whole sparse bundle; copy the Backups.backupdb folder from the sparse bundle to the top level of the HD. (Sparse bundles are used only for network backups.) See #18 in the FAQ; you'll need the 4th procedure (copy network backups to be used locally.
But if you're going to connect the HD to the TC and back up to it that way, it doesn't matter how you format the HD, since the backups must be in a sparse bundle, that has its own format. Two choices for that:
* Leave the TC backups alone. Connect the HD to the TC and select it as the TM destination, and Let Time Machine start fresh on it. You can always see and restore from the old ones via the Browse... option, as above.   (There is a way to speed up the first backup; see the blue box in #Q2 of Using Time Machine with a Time Capsule.)
* Copy ("Archive") the TC's internal disk to the external HD, per the green box in #Q6 of the same article. Then select the external as your Time Machine destination via Time Machine Preferences.
Is this simply deferring a problem issue to another time (aagh)? Or to somehow try and remove this inconsistency and remove case-sensitive formatting from all tech items, even if this might mean reformatting and losing old backup data?
No. There's not really a problem, unless you change the case of file/folder names and try to restore the old ones to the same place via the TM browser, per the link in my earlier post. That's the only possible downside.
Does Time Machine require case-sensitive formatting on its destination drive?
No. It's the default, but case-ignorant is fine, unless you ever want to add a case-sensitive volume. Then you're in a pickle.
Or does Time Capsule only function witih case-sensitive formatting?
No. The TC's actual disk is case-ignorant; it's only the Time Machine sparse bundle that's case-sensitive by default.
The benefit of case-sensitive formatting as Apple default seems rather unclear to me
It's the default only for Time Machine backups. Everything else defaults to case-ignorant.
The advantage is, once you've been backing-up your internal HD for weeks, months, or years, and want to add a case-sensitive external HD to be backed-up, you can.   If the backups are case-ignorant, you can't.

Change Case-sensitivity of field ASKTX in Search Help ASMD

Hi experts,
In Collective Search help ASMD, there is a elementory search help /SAPBOQ/ASMD_MITEM where field ASKTX is Case sensitive.
How can I remove the case-sensitivity of this field ?
Thnks in advance,
Goutam

owngoal wrote:
You say your "backups still turn up corrupted now and then" - how do you know? Is it only when you try to access them that you will know this?
Sometimes a backup will fail, sometimes you can't access them, sometimes you'll get this message:
See #C13 in Time Machine - Troubleshooting for details.
And by this stage is it too late to recover anything?
Sometimes. Sometimes they can be repaired by Disk Utility. Sometimes only a heavy-duty 3rd-party disk repair app like DiskWarrior ($100) can fix them. Sometimes nothing can. Sometimes you can restore some individual items, sometimes not. Sometimes you can do a full system restore from some backups, other times not.
does it help that I am using a Gigabit WIRED connection between iMac - 10/100/1000 switch - Airport Extreme Base Station?
Probably -- you won't have WIFI interference.
But if you have an iMac, why not just connect the external HD directly to your Mac? That's much faster and more reliable (and supported).
You'd need to erase the disk in that case, since Time Machine won't bother with a sparse bundle at all on a direct backup. Just format the disk as GUID, with Mac OS Extended (Journaled) and let 'er rip!

Case Sensitive problem in Select Option for wild card search

Hi,
Can anyone please let me know how to make the wild card search in any select-option non case-sensitive. What I mean by this is for eg. we want to find out all the POs with short text containing the word 'process', what we do we populate a range with OPTION = 'CP' and LOW = 'process' and select EKPO with short text in this range. This select is however case-sensitive and POs with short text containing 'Process' is not retrieved. But my requirement is that this should be non case-sensitive and both the POs should be in the result set.

Hi,
Hope this helps you
CS:
You can select characters in operand2 for a direct comparison by adding the escape symbol "#" before the required characters. For these characters, upper/lower case is taken into account, wildcard characters and the escape symbol itself do not receive special treatment, and trailing blanks in operands of type c are not cut off.
Covers Pattern: True, if the content of operand1 fits the pattern in operand2. Wildcard characters can be used for forming the operand pattern, where "" represents any character string, and "+" represents any character. Upper/lower case is not taken into account. If the comparison is true, sy-fdpos contains the offset of operand2 in operand1, whereby leading wildcard characters "" in operand2 are ignored if operand2 also contains other characters. If the comparison is false, sy-fdpos contains the length of operand1.
Regards
Krishna

Calling a function module in Case Sensitive mode

Hi,
How to call a FM from a report so that the values that character values that are passed to FM are NOT automatically converted to Upper case instead the entries are case sensitive.
Like when we execute the FM from SE37 There is a checkbox
Uppercase/Lowercase at Test Function Module: Initial Screen.
Thanks,
Anubhav
Sorry If this is a basic question, I searched but could not find relevant thread.

You don't need any additional coding for this. If you pass a case senistive text to a FM (in a report) the text remains case-sensitive.
The "Uppercase/Lowercase" checkbox is applicable for direct testing via SE37.

Change from case-sensitive disk format to the normal Mac OS Extended.

Hi,
I need to change from a case-sensitive disk format to the normal Mac OS Extended Journaled version.
I have no external HD fitted, but I do have some DVD-Rs. I need to restore the data from 2 users, including iTunes and iPhoto files.
What's the best way to achieve this?
Many thanks,
Tris.

I just got off of the phone with Adobe support. They told me they knew the solution, but that they would not tell me tonight. I had to call back between 6:00 am and 5:00 PM tomorrow. That does not work with my schedule. So I googled some stuff and found that Adobe CS 3 is not supported with Case-Sensitive file systems. So OK, let me install this to my other MAC that has a non case sensitive drive. Same error. Even though I have a non case-sensitive drive, the OS is on a Case-Sensitive Drive and I am never prompted where to install like most all other Mac Software.
I have always formatted case-sensitive. So I am thinking to myself why not start using a non case-sensitive drive. Well, to start off I want it case sensitive. I enjoy web programming and like this feature. Sure it is not needed, but I am glad Apple offered me a choice. And I am sure there are many other reasons why to use it. Also I would be interested in knowing why non case-sensitive drives are supperior.
Why is this a requirement now? I have used Adobe software in the past without this specific issue. I also have Large TB drives and do not know how to 'safely' do this. You will not catch me jumping through this hoop. I will not risk the change to the file system. And I can not be expected to format my drive. I just wonder what Adobe would say tomorrow if I called.
The Direct line I was given by adobe is 800-642-3623 for support on this issue. You don't need anything else but to call this number and ask. You can not get through after hours though.
Wow, I just can't believe this and the lack of interest Adobe had with me.
I hope I can get a refund on the software. Until I am able to downgrade my file system format, I do not want to sit on Adobe's bill. I will buy it again assuming I learn I can't do without PS CS3.

Case sensitive data

Hi,
Running on MS-SQL and creating a user defined field is it then possible to set collation to CS instead of default CI (Case Insensitive).
Of course you can always do this from EM, but when patching the database this setting will be lost.
I've noticed when creating a new company the collation of database will be set to "SQL_Latin1_General_CP850_CI_AS".
Is there anyway to change default collation to "SQL_Latin1_General_CP850_<b>CS</b>_AS" ??
Soren

Well, I need to do this as some of my data is case sensitive
Say: AAABCI differs from AAABCi
And yes, when patching a SBO with a CS key field on a user defined table will course the pathing to fail.
The data is imported from a remote system (R3) and is crutial for a series of add-ons using this master data.
There is no way of doing direct queries in the remote system.

Case Sensitive ColumnNames

Hello,
When I have the following query as example:
select sysdate "SystemDateTime" from dual;
Retrieving the table columnname with MetaData::ATTR_NAME gives me "SYSDATETIME" in stead of "SystemDateTime". It doesn't give a case sensitive table columnname back although I mentioned it in the query.
Is this normal behaviour?
Rodger

Can you post your code?. I get the correct mixed case column alias with this code :-
Statement *stmt = conn->createStatement("select sysdate \"AbCd\" from dual");
ResultSet *rs = stmt->executeQuery();
vector<MetaData> md = rs->getColumnListMetaData();
cout << "Column " << md[0].getString(MetaData::ATTR_NAME) << endl;
Regards.

Oracel Link server is case sensitive

Hi,
I had created a Link server for with oracle . it working fine ,only issue is table name are case sensitive.
when i run Select * from temp , it is running directly in oracle but when i try to run this by link server it says temp table don't not exists .
And if i Write Select * from TEMP then it works. Can any one know how to fix this issue case it very difficult to remember table name with case.

Hi Mujahid.hassan,
Thank you for your update. As I mentioned above the collation of an identifier depends on the level at which it is defined. The database name is sever level collation and is assigned the default collation of the instance.
The server collation acts as the default collation for all system databases that are installed with the instance of SQL Server, and also any newly created user databases. The server collation is specified during SQL Server installation
If you want to change the server level collation you need to rebuild your system databases. For how to Setting and Changing the Server Collation, please follow the steps in changing the server collation section from
here.
Regards, Amber zhang

Alias directive case-sensitive?

Similar Messages

Maybe you are looking for