Oracle XML DB server charset

Question

Hi, how do I change a Oracle XML DB (embedded gateway) server's charset and make it e.g. UFT-8?
Thanks,
Art
Edited by: ArtS on Apr 21, 2011 11:27 AM

Answer 1

ArtS wrote:
No, it's not. Here is what a google boot sees.
HTTP/1.1 302 Found
Date: Tue, 18 Jan 2011 15:48:40 GMT
Server: Oracle XML DB/Oracle Database
Location: http://xxxxxxxxxxxxxxxxxxxxxx
Vary: Accept-Encoding,User-Agent
Content-Encoding: gzip
Content-Length: 20
Keep-Alive: timeout=2, max=500
Connection: Keep-Alive
Content-Type: text/plain; charset=ISO-8859-2As I see it's a 302 page (redirection)
Could you also test a valid apex page? Here's the one from a sample page hosted at apex.oracle.com:
HTTP/1.1 200 OK
Date: Fri, 22 Apr 2011 20:14:22 GMT
Server: Oracle-Application-Server-11g
Connection: close
Content-Type: text/html; charset=UTF-8
Content-Language: en
Set-Cookie: BIGipServerapex-ext_oracle_com_http=XXXXXXXXXXXXXXXXXX; path=/
and here's a forward (302) page on same server:
HTTP/1.1 302 Found
Date: Fri, 22 Apr 2011 20:17:03 GMT
Server: Oracle-Application-Server-11g
Location: f?p=XXXXXXXXXXXXXXXXXXXXXXXXXXXXX
Content-Length: 0
Connection: close
Content-Type: text/plain
Content-Language: en
Set-Cookie: BIGipServerapex-ext_oracle_com_http=XXXXXXXXXXXXXXX; path=/
I got this one (one same server and for same page when I tried to trace):
HTTP/1.1 405 Method Not Allowed
Date: Fri, 22 Apr 2011 20:20:55 GMT
Server: Oracle-Application-Server-11g
Allow:
Content-Length: 253
Connection: close
Content-Type: text/html; charset=iso-8859-1
Set-Cookie: BIGipServerapex-ext_oracle_com_http=XXXXXXXXXXXXXXXX; path=/
So as I see, it sends "charset=iso-8859-1" on error pages, "none" on forwarding, "utf-8" for real pages. In fact, APEX 4 already publishes pages in utf-8 charset. Here's nother apex web site:
HTTP/1.1 200 OK
Date: Fri, 22 Apr 2011 18:01:56 GMT
Server: Oracle XML DB/Oracle Database
Content-Type: text/html; charset=UTF-8
Content-Length: 54491
Connection: close
And here's a brief explanation about meta Content-Type:
A known misconception about <meta http-equiv="Content-Type"> is that this attribute of meta element is intended to be interpreted directly by a browser, like an ordinary HTML tag. According to WWW Consortium, it helps the HTTP server to generate corresponding headers when it serves the document. The HTTP/1.1 header specification for a HTML document must label an appropriate encoding in the Content-Type header, missing charset= parameter results in acceptance of ISO-8859-1 (so HTTP/1.1 formally does not offer such option as an unspecified character encoding), and this specification supersedes all HTML (or XHTML) meta element ones. This can pose a problem if the server generates an incorrect header and one does not have the access or the knowledge to change them.
I hope it helps!
Best Regards,
Gokhan
If this question is answered, please mark appropriate posts as correct/helpful and the thread as closed. Thanks