What characters Cannot be used in a URL?
ASCII control characters (e.g. backspace, vertical tab, horizontal tab, line feed etc), unsafe characters like space , \ , < , > , { , } etc, and any character outside the ASCII charset is not allowed to be placed directly within URLs.
Can you use Japanese characters?
Yes, it’s true. Japanese has three completely separate sets of characters, called kanji, hiragana, and katakana, that are used in reading and writing. In other words, hiragana characters function like English letters, in that they don’t have any intrinsic meaning. They just represent sounds.
What are the safe characters for making friendly URL?
There are two sets of characters you need to watch out for: reserved and unsafe. question mark (“?”) pound (“#”). The characters generally considered unsafe are: I may have forgotten one or more, which leads to me echoing Carl V’s answer.
Is it OK to use no accent in an url?
Maybe URL with no accent are not looking the best that could be ; but, still, people are used to them, and seem to generally understand them quite well. You should avoid non-ASCII characters in URLs that may be entered in browser manually by users. It’s ok for embedded links pre-encoded by server.
Why are there no Unicode chars in URLs?
What appears to be unicode chars in URLs is really only ‘visual sugar’ on the part of the browser: if you use a browser that doesn’t support IDN or unicode, the encoded version won’t work because the underlying definition of URLs simply doesn’t support it, so for it to work consistently, you need to % encode.
Is it safe to use safe characters in a string?
In the long run you are probably better off using a “white list” of allowed characters and then encoding the string rather than trying to stay abreast of characters that are disallowed by servers and systems. In theory and by the specification, these are safe basically anywhere, except the domain name.