htaccess and unicode (the letter 'נ')?
up vote
0
down vote
favorite
I have an htaccess file which contains some rewriting rules, for friendly urls.
everything is working fine, except if I use the letter 'נ'
in hebrew.
Line (1) is working, line (2) isn't:
RewriteRule ^א$ file.ext
RewriteRule ^נ$ file.ext
I simply get a 500 error.
(I use wamp + win xp.pro)
.htaccess unicode wamp hebrew
add a comment |
up vote
0
down vote
favorite
I have an htaccess file which contains some rewriting rules, for friendly urls.
everything is working fine, except if I use the letter 'נ'
in hebrew.
Line (1) is working, line (2) isn't:
RewriteRule ^א$ file.ext
RewriteRule ^נ$ file.ext
I simply get a 500 error.
(I use wamp + win xp.pro)
.htaccess unicode wamp hebrew
Do you get the 500 error when you put the letter into .htaccess or into your browser?
– Roman Starkov
Jan 9 '11 at 13:19
it's in the htaccess file
– yossi
Jan 9 '11 at 14:24
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have an htaccess file which contains some rewriting rules, for friendly urls.
everything is working fine, except if I use the letter 'נ'
in hebrew.
Line (1) is working, line (2) isn't:
RewriteRule ^א$ file.ext
RewriteRule ^נ$ file.ext
I simply get a 500 error.
(I use wamp + win xp.pro)
.htaccess unicode wamp hebrew
I have an htaccess file which contains some rewriting rules, for friendly urls.
everything is working fine, except if I use the letter 'נ'
in hebrew.
Line (1) is working, line (2) isn't:
RewriteRule ^א$ file.ext
RewriteRule ^נ$ file.ext
I simply get a 500 error.
(I use wamp + win xp.pro)
.htaccess unicode wamp hebrew
.htaccess unicode wamp hebrew
edited Nov 11 at 3:18
Cœur
17k9102140
17k9102140
asked Jan 9 '11 at 13:08
yossi
1,59233351
1,59233351
Do you get the 500 error when you put the letter into .htaccess or into your browser?
– Roman Starkov
Jan 9 '11 at 13:19
it's in the htaccess file
– yossi
Jan 9 '11 at 14:24
add a comment |
Do you get the 500 error when you put the letter into .htaccess or into your browser?
– Roman Starkov
Jan 9 '11 at 13:19
it's in the htaccess file
– yossi
Jan 9 '11 at 14:24
Do you get the 500 error when you put the letter into .htaccess or into your browser?
– Roman Starkov
Jan 9 '11 at 13:19
Do you get the 500 error when you put the letter into .htaccess or into your browser?
– Roman Starkov
Jan 9 '11 at 13:19
it's in the htaccess file
– yossi
Jan 9 '11 at 14:24
it's in the htaccess file
– yossi
Jan 9 '11 at 14:24
add a comment |
1 Answer
1
active
oldest
votes
up vote
3
down vote
accepted
A browser like Firefox would encode such characters, usually using UTF-8. So the web server would receive "%D7%A0" in the URL instead of this character.
Try putting that into your .htaccess rule instead of the character itself:
RewriteRule ^%D7%90$ file.ext
RewriteRule ^%D7%A0$ file.ext
It could also be that your web application doesn't know how to handle UTF-8 encoded URLs and so gives you a 500 error message.
and other browsers will "understand" it?
– yossi
Jan 9 '11 at 14:25
@yossi it depends. Up until very recently there was simply no way at all to have such letters in the URL. A couple of years ago (maybe even less) Firefox started to show such URLs in "decoded", human-readable form. You can test if your browser supports this by going to the Hebrew wikipedia and looking at the URL bar, to see if it has hebrew characters or stuff like %D7%A7%D7.
– Roman Starkov
Jan 9 '11 at 14:46
@romkyns: Don't look at the URL bar, look at the reality. The URL bar "beautifies" the URL. To get the real URL, go to the URL bar, select the whole URL and copy it into the clipboard. Then, paste it whereever you want, for example in anotepad
window.
– Roland Illig
Jan 9 '11 at 17:15
@Roland I know, not sure what your point is though.
– Roman Starkov
Jan 9 '11 at 17:36
2
My point is that URLs still only consist of ASCII characters, no matter what Firefox displays in the "URL bar". (That comment didn't aim at you personally but at those readers who might think that URLs may contain arbitrary characters by now. I felt your comment suggested that.)
– Roland Illig
Jan 9 '11 at 22:10
|
show 3 more comments
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
3
down vote
accepted
A browser like Firefox would encode such characters, usually using UTF-8. So the web server would receive "%D7%A0" in the URL instead of this character.
Try putting that into your .htaccess rule instead of the character itself:
RewriteRule ^%D7%90$ file.ext
RewriteRule ^%D7%A0$ file.ext
It could also be that your web application doesn't know how to handle UTF-8 encoded URLs and so gives you a 500 error message.
and other browsers will "understand" it?
– yossi
Jan 9 '11 at 14:25
@yossi it depends. Up until very recently there was simply no way at all to have such letters in the URL. A couple of years ago (maybe even less) Firefox started to show such URLs in "decoded", human-readable form. You can test if your browser supports this by going to the Hebrew wikipedia and looking at the URL bar, to see if it has hebrew characters or stuff like %D7%A7%D7.
– Roman Starkov
Jan 9 '11 at 14:46
@romkyns: Don't look at the URL bar, look at the reality. The URL bar "beautifies" the URL. To get the real URL, go to the URL bar, select the whole URL and copy it into the clipboard. Then, paste it whereever you want, for example in anotepad
window.
– Roland Illig
Jan 9 '11 at 17:15
@Roland I know, not sure what your point is though.
– Roman Starkov
Jan 9 '11 at 17:36
2
My point is that URLs still only consist of ASCII characters, no matter what Firefox displays in the "URL bar". (That comment didn't aim at you personally but at those readers who might think that URLs may contain arbitrary characters by now. I felt your comment suggested that.)
– Roland Illig
Jan 9 '11 at 22:10
|
show 3 more comments
up vote
3
down vote
accepted
A browser like Firefox would encode such characters, usually using UTF-8. So the web server would receive "%D7%A0" in the URL instead of this character.
Try putting that into your .htaccess rule instead of the character itself:
RewriteRule ^%D7%90$ file.ext
RewriteRule ^%D7%A0$ file.ext
It could also be that your web application doesn't know how to handle UTF-8 encoded URLs and so gives you a 500 error message.
and other browsers will "understand" it?
– yossi
Jan 9 '11 at 14:25
@yossi it depends. Up until very recently there was simply no way at all to have such letters in the URL. A couple of years ago (maybe even less) Firefox started to show such URLs in "decoded", human-readable form. You can test if your browser supports this by going to the Hebrew wikipedia and looking at the URL bar, to see if it has hebrew characters or stuff like %D7%A7%D7.
– Roman Starkov
Jan 9 '11 at 14:46
@romkyns: Don't look at the URL bar, look at the reality. The URL bar "beautifies" the URL. To get the real URL, go to the URL bar, select the whole URL and copy it into the clipboard. Then, paste it whereever you want, for example in anotepad
window.
– Roland Illig
Jan 9 '11 at 17:15
@Roland I know, not sure what your point is though.
– Roman Starkov
Jan 9 '11 at 17:36
2
My point is that URLs still only consist of ASCII characters, no matter what Firefox displays in the "URL bar". (That comment didn't aim at you personally but at those readers who might think that URLs may contain arbitrary characters by now. I felt your comment suggested that.)
– Roland Illig
Jan 9 '11 at 22:10
|
show 3 more comments
up vote
3
down vote
accepted
up vote
3
down vote
accepted
A browser like Firefox would encode such characters, usually using UTF-8. So the web server would receive "%D7%A0" in the URL instead of this character.
Try putting that into your .htaccess rule instead of the character itself:
RewriteRule ^%D7%90$ file.ext
RewriteRule ^%D7%A0$ file.ext
It could also be that your web application doesn't know how to handle UTF-8 encoded URLs and so gives you a 500 error message.
A browser like Firefox would encode such characters, usually using UTF-8. So the web server would receive "%D7%A0" in the URL instead of this character.
Try putting that into your .htaccess rule instead of the character itself:
RewriteRule ^%D7%90$ file.ext
RewriteRule ^%D7%A0$ file.ext
It could also be that your web application doesn't know how to handle UTF-8 encoded URLs and so gives you a 500 error message.
edited Jan 10 '11 at 10:25
answered Jan 9 '11 at 13:19
Roman Starkov
34.2k24186270
34.2k24186270
and other browsers will "understand" it?
– yossi
Jan 9 '11 at 14:25
@yossi it depends. Up until very recently there was simply no way at all to have such letters in the URL. A couple of years ago (maybe even less) Firefox started to show such URLs in "decoded", human-readable form. You can test if your browser supports this by going to the Hebrew wikipedia and looking at the URL bar, to see if it has hebrew characters or stuff like %D7%A7%D7.
– Roman Starkov
Jan 9 '11 at 14:46
@romkyns: Don't look at the URL bar, look at the reality. The URL bar "beautifies" the URL. To get the real URL, go to the URL bar, select the whole URL and copy it into the clipboard. Then, paste it whereever you want, for example in anotepad
window.
– Roland Illig
Jan 9 '11 at 17:15
@Roland I know, not sure what your point is though.
– Roman Starkov
Jan 9 '11 at 17:36
2
My point is that URLs still only consist of ASCII characters, no matter what Firefox displays in the "URL bar". (That comment didn't aim at you personally but at those readers who might think that URLs may contain arbitrary characters by now. I felt your comment suggested that.)
– Roland Illig
Jan 9 '11 at 22:10
|
show 3 more comments
and other browsers will "understand" it?
– yossi
Jan 9 '11 at 14:25
@yossi it depends. Up until very recently there was simply no way at all to have such letters in the URL. A couple of years ago (maybe even less) Firefox started to show such URLs in "decoded", human-readable form. You can test if your browser supports this by going to the Hebrew wikipedia and looking at the URL bar, to see if it has hebrew characters or stuff like %D7%A7%D7.
– Roman Starkov
Jan 9 '11 at 14:46
@romkyns: Don't look at the URL bar, look at the reality. The URL bar "beautifies" the URL. To get the real URL, go to the URL bar, select the whole URL and copy it into the clipboard. Then, paste it whereever you want, for example in anotepad
window.
– Roland Illig
Jan 9 '11 at 17:15
@Roland I know, not sure what your point is though.
– Roman Starkov
Jan 9 '11 at 17:36
2
My point is that URLs still only consist of ASCII characters, no matter what Firefox displays in the "URL bar". (That comment didn't aim at you personally but at those readers who might think that URLs may contain arbitrary characters by now. I felt your comment suggested that.)
– Roland Illig
Jan 9 '11 at 22:10
and other browsers will "understand" it?
– yossi
Jan 9 '11 at 14:25
and other browsers will "understand" it?
– yossi
Jan 9 '11 at 14:25
@yossi it depends. Up until very recently there was simply no way at all to have such letters in the URL. A couple of years ago (maybe even less) Firefox started to show such URLs in "decoded", human-readable form. You can test if your browser supports this by going to the Hebrew wikipedia and looking at the URL bar, to see if it has hebrew characters or stuff like %D7%A7%D7.
– Roman Starkov
Jan 9 '11 at 14:46
@yossi it depends. Up until very recently there was simply no way at all to have such letters in the URL. A couple of years ago (maybe even less) Firefox started to show such URLs in "decoded", human-readable form. You can test if your browser supports this by going to the Hebrew wikipedia and looking at the URL bar, to see if it has hebrew characters or stuff like %D7%A7%D7.
– Roman Starkov
Jan 9 '11 at 14:46
@romkyns: Don't look at the URL bar, look at the reality. The URL bar "beautifies" the URL. To get the real URL, go to the URL bar, select the whole URL and copy it into the clipboard. Then, paste it whereever you want, for example in a
notepad
window.– Roland Illig
Jan 9 '11 at 17:15
@romkyns: Don't look at the URL bar, look at the reality. The URL bar "beautifies" the URL. To get the real URL, go to the URL bar, select the whole URL and copy it into the clipboard. Then, paste it whereever you want, for example in a
notepad
window.– Roland Illig
Jan 9 '11 at 17:15
@Roland I know, not sure what your point is though.
– Roman Starkov
Jan 9 '11 at 17:36
@Roland I know, not sure what your point is though.
– Roman Starkov
Jan 9 '11 at 17:36
2
2
My point is that URLs still only consist of ASCII characters, no matter what Firefox displays in the "URL bar". (That comment didn't aim at you personally but at those readers who might think that URLs may contain arbitrary characters by now. I felt your comment suggested that.)
– Roland Illig
Jan 9 '11 at 22:10
My point is that URLs still only consist of ASCII characters, no matter what Firefox displays in the "URL bar". (That comment didn't aim at you personally but at those readers who might think that URLs may contain arbitrary characters by now. I felt your comment suggested that.)
– Roland Illig
Jan 9 '11 at 22:10
|
show 3 more comments
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f4639245%2fhtaccess-and-unicode-the-letter-%25d7%25a0%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Do you get the 500 error when you put the letter into .htaccess or into your browser?
– Roman Starkov
Jan 9 '11 at 13:19
it's in the htaccess file
– yossi
Jan 9 '11 at 14:24