10:48 p.m.
MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------
Key: JBWS-2405
URL: https://jira.jboss.org/jira/browse/JBWS-2405
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA
(build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun
Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
Reporter: Chyi Pin Lim
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the
attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750"
xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under
the test suite to simulate this error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:54 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode
[
https://jira.jboss.org/jira/browse/JBWS-2405?page=com.atlassian.jira.plug...
]
Chyi Pin Lim updated JBWS-2405:
-------------------------------
Attachment: jboss-mtom-xop-cid-decode.patch
I patched it up so that it works on my local deployment.
So far, the changes is local to a single file for simplicity. The implementation is
straight forward, by decoding the both the cid and the contentId url and then comparing
them. I'm sure there's plenty of room for improvement.
Based on RFC 2392, I don't know if WCF is correct or JBoss is correct. However, I
think for a specific url, both the un-encoded url or the url-encoded url should be the
same.
MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------
Key: JBWS-2405
URL: https://jira.jboss.org/jira/browse/JBWS-2405
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA
(build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun
Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
Reporter: Chyi Pin Lim
Attachments: jboss-mtom-xop-cid-decode.patch
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the
attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750"
xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under
the test suite to simulate this error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:24 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode
[
https://jira.jboss.org/jira/browse/JBWS-2405?page=com.atlassian.jira.plug...
]
Greg Bailey updated JBWS-2405:
------------------------------
Attachment: jbossws-native-2.0.1.SP2-mtom-xop-cid-decode.patch
A copy of the prior attachment "jboss-mtom-xop-cid-decode.patch" but modified
for JBoss WS 2.0.1.SP2 that is bundled with JBoss AS 4.2.2.GA.
MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------
Key: JBWS-2405
URL: https://jira.jboss.org/jira/browse/JBWS-2405
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA
(build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun
Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
Reporter: Chyi Pin Lim
Attachments: jboss-mtom-xop-cid-decode.patch,
jbossws-native-2.0.1.SP2-mtom-xop-cid-decode.patch
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the
attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750"
xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under
the test suite to simulate this error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:45 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode
[
https://jira.jboss.org/jira/browse/JBWS-2405?page=com.atlassian.jira.plug...
]
Greg Bailey updated JBWS-2405:
------------------------------
Attachment: jbossws-3.0.1-native-2.0.4.GA-mtom-xop-cid-decode.patch
A copy of the prior attachment "jboss-mtom-xop-cid-decode.patch" but modified
for JBoss WS 2.0.4 that is bundled with JBoss AS 4.2.3.GA.
MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------
Key: JBWS-2405
URL: https://jira.jboss.org/jira/browse/JBWS-2405
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA
(build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun
Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
Reporter: Chyi Pin Lim
Attachments: jboss-mtom-xop-cid-decode.patch,
jbossws-3.0.1-native-2.0.4.GA-mtom-xop-cid-decode.patch,
jbossws-native-2.0.1.SP2-mtom-xop-cid-decode.patch
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the
attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750"
xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under
the test suite to simulate this error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
7:20 a.m.
New subject: [JBoss JIRA] Updated: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode
[
https://jira.jboss.org/jira/browse/JBWS-2405?page=com.atlassian.jira.plug...
]
Richard Opalka updated JBWS-2405:
---------------------------------
Fix Version/s: jbossws-native-3.1.1
MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------
Key: JBWS-2405
URL: https://jira.jboss.org/jira/browse/JBWS-2405
Project: JBoss Web Services
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA
(build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun
Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
Reporter: Chyi Pin Lim
Assignee: Richard Opalka
Fix For: jbossws-native-3.1.1
Attachments: jboss-mtom-xop-cid-decode.patch,
jbossws-3.0.1-native-2.0.4.GA-mtom-xop-cid-decode.patch,
jbossws-native-2.0.1.SP2-mtom-xop-cid-decode.patch
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the
attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750"
xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under
the test suite to simulate this error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:11 p.m.
New subject: [JBoss JIRA] Updated: (JBWS-2405) MTOM/XOP Interoperability - cid href URLEncode/URLDecode
[
https://jira.jboss.org/jira/browse/JBWS-2405?page=com.atlassian.jira.plug...
]
Stelios Koussouris updated JBWS-2405:
-------------------------------------
Issue Type: Bug (was: Feature Request)
In accordance to the following case we have agreed that this is now a bug
https://enterprise.redhat.com/issue-tracker/?module=issues&action=vie...
MTOM/XOP Interoperability - cid href URLEncode/URLDecode
--------------------------------------------------------
Key: JBWS-2405
URL: https://jira.jboss.org/jira/browse/JBWS-2405
Project: JBoss Web Services
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: jbossws-native
Affects Versions: jbossws-native-3.0.4
Environment: 14:36:53,328 INFO [Server] Release ID: JBoss [Trinity] 4.2.2.GA
(build: SVNTag=JBoss_4_2_2_GA date=200710221139)
14:36:56,109 INFO [ServerInfo] Java version: 1.5.0_14,Sun Microsystems Inc.
14:36:56,109 INFO [ServerInfo] Java VM: Java HotSpot(TM) Client VM 1.5.0_14-b03,Sun
Microsystems Inc.
14:36:56,109 INFO [ServerInfo] OS-System: Windows XP 5.1,x86
14:37:27,656 INFO [NativeServerConfig] JBoss Web Services - Stack Native Core
14:37:27,656 INFO [NativeServerConfig] 3.0.4.GA
Reporter: Chyi Pin Lim
Assignee: Richard Opalka
Fix For: jbossws-native-3.1.1
Attachments: jboss-mtom-xop-cid-decode.patch,
jbossws-3.0.1-native-2.0.4.GA-mtom-xop-cid-decode.patch,
jbossws-native-2.0.1.SP2-mtom-xop-cid-decode.patch
WCF uses a URL Encoded href cid for xopInclude. However, the Content-Id for the
attachment is not URL Encoded. As such, JBossWS is unable to find the attachment.
Example:
<xop:Include href="cid:http%3A%2F%2Ftempuri.org%2F1%2F633631227250468750"
xmlns:xop="http://www.w3.org/2004/08/xop/include"/>
--uuid:357c6d9d-d6cf-42e3-bca5-75c8f3761934+id=1
Content-ID: <http://tempuri.org/1/633631227250468750>
Since this is an interoperability issue, I don't know how to create a test case under
the test suite to simulate this error.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5491
days inactive
5632
days old
jbossws-issues@lists.jboss.org
5 comments
4 participants
participants (4)
-
Chyi Pin Lim (JIRA) -
Greg Bailey (JIRA)
-
Richard Opalka (JIRA)
-
Stelios Koussouris (JIRA)