401 REST Adapter When Using A ".xml" Extension In URL
(Doc ID 2832856.1)
Last updated on SEPTEMBER 24, 2023
Applies to:
Oracle SOA Suite - Version 12.2.1.3.0 and laterInformation in this document applies to any platform.
Symptoms
On : 12.2.1.3.0 version, Fabric
ACTUAL BEHAVIOR
---------------
401 REST Adapter when using a ".xml" extension in URL
A REST endpoint is exposed in SOA Suite, with a resource /trainxml/{filename} where filename is dynamic and is filled by client using the filename with extension.
When is set a value like "123.xml", with extension xml, the SOA Suite is rejecting the request with a 401 unauthorized response.
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Draft//EN">
<HTML>
<HEAD>
<TITLE>Error 401--Unauthorized</TITLE>
<META NAME="GENERATOR" CONTENT="WebLogic Server">
</HEAD>
<BODY bgcolor="white">
<FONT FACE=Helvetica><BR CLEAR=all>
<TABLE border=0 cellspacing=5><TR><TD><BR
CLEAR=all>
<FONT FACE="Helvetica" COLOR="black" SIZE="3"><H2>Error
401--Unauthorized</H2>
</FONT></TD></TR>
</TABLE>
<TABLE border=0 width=100% cellpadding=10><TR><TD
VALIGN=top WIDTH=100% BGCOLOR=white><FONT FACE="Courier New">
<FONT FACE="Helvetica" SIZE="3"><H3>From RFC 2068 <i>
Hypertext Transfer Protocol – HTTP/1.1</i>:</H3>
</FONT><FONT FACE="Helvetica" SIZE="3"><H4>10.4.2 401
Unauthorized</H4>
</FONT><P><FONT FACE="Courier New">The request
requires user authentication. The response MUST include a
WWW-Authenticate header field (section 14.46) containing a challenge
applicable to the requested resource. The client MAY repeat the request
with a suitable Authorization header field (section 14.8). If the
request already included Authorization credentials, then the 401
response indicates that authorization has been refused for those
credentials. If the 401 response contains the same challenge as the
prior response, and the user agent has already attempted authentication
at least once, then the user SHOULD be presented the entity that was
given in the response, since that entity MAY include relevant diagnostic
information. HTTP access authentication is explained in section 11.<
/FONT></P>
</FONT></TD></TR>
</TABLE>
</BODY>
</HTML>
--------------------------------------------
The issue is not occurring when another extension is set, for example ".html".
EXPECTED BEHAVIOR
-----------------------
The REST exposed endpoint to accept ".xml" extension
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Cause |
| Solution |
| References |