Http-Oxta Is Not Used When The Previous Message Has Http-Atch.
(Doc ID 558983.1)
Last updated on APRIL 04, 2025
Applies to:
Oracle XML Gateway - Version 11.5.10.2 to 11.5.10.4 [Release 11.5.10]Information in this document applies to any platform.
Symptoms
-- Problem Statement:
When an HTTP-OXTA XML message is delivered straight after an HTTP-ATCH XML message, the protocol will remain plain HTTP and doesn't switch to OXTA.
Response: HTTP/1.1 400 Bad Request
Date: Tue, 23 Oct 2007 15:04:42 GMT
Content-Type: text/html; charset=iso-8859-1
X-Cache: MISS from emaf11t.mit.gbr.xerox.com
Connection: close
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>400 Bad Request</TITLE>
</HEAD><BODY>
<H1>Bad Request</H1>
Your browser sent a request that this server could not understand.<P>
</BODY></HTML>
-- Steps To Reproduce:
Generate two XML messages after each other where the first is HTTP-ATCH and the second is HTTP-OXTA, delivery of the OXTA message will fail until there is no HTTP-ATCH in the same processing cycle. These messages must be generated very close to each other to ensure they are in the same processing cycle.
Changes
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 |
| Changes |
| Cause |
| Solution |
| References |