You are viewing a plain text version of this content. The canonical link for it is here.
Posted to soap-dev@ws.apache.org by ji...@apache.org on 2004/04/05 15:46:43 UTC

[jira] Closed: (SOAP-162) Must drop trailing whitespace from HTTP headers.

Message:

   The following issue has been closed.

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/SOAP-162

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: SOAP-162
    Summary: Must drop trailing whitespace from HTTP headers.
       Type: Bug

     Status: Closed
 Resolution: FIXED

    Project: Apache SOAP
 Components: 
             All
   Versions:
             2.3

   Assignee: Scott Nichol
   Reporter: Scott Nichol

    Created: Wed, 14 Jan 2004 9:08 PM
    Updated: Mon, 5 Apr 2004 6:44 AM
Environment: Operating System: All
Platform: All

Description:
Hi,
since a customer has changed his firewall, Proxy-Software and so on,
he gets Exceptions like this one below, when he tries to use our application
which performs RPC-calls via SOAP.

[SOAPException: faultCode=SOAP-ENV:Client; msg=Error parsing HTTP header
line "Content-Length: 3957  ": java.lang.NumberFormatException: 3957  ;
targetException=java.lang.NumberFormatException: 3957  ]
at org.apache.soap.util.net.HTTPUtils.post(Unknown Source)
at org.apache.soap.util.net.HTTPUtils.post(Unknown Source)
at org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown Source)
at org.apache.soap.rpc.Call.invoke(Unknown Source)
at org.apache.soap.rpc.Call.invoke(Unknown Source)
at
de.mc.etnbestterm.data.SoapCallingDataHolder.callSoaply(SoapCallingDataHolde
r.java:75)
at
de.mc.etnbestterm.data.MainDataHolder.connectServerToDB(MainDataHolder.java:
457)
at de.mc.etnbestterm.data.MainDataHolder.<init>(MainDataHolder.java:61)
at
de.mc.etnbestterm.data.SingletonManager.getMainDataHolder(SingletonManager.j
ava:49)
at de.mc.etnbestterm.gui.WillkommenPanel.jbInit(WillkommenPanel.java:62)
at de.mc.etnbestterm.gui.WillkommenPanel.<init>(WillkommenPanel.java:52)
at de.mc.etnbestterm.gui.MainFrame.<init>(MainFrame.java:40)
at de.mc.etnbestterm.Bestellterminal.jbInit(Bestellterminal.java:67)
at de.mc.etnbestterm.Bestellterminal.<init>(Bestellterminal.java:45)
at de.mc.etnbestterm.Bestellterminal.main(Bestellterminal.java:119)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)
Caused by: java.lang.NumberFormatException: 3957
at java.lang.Integer.parseInt(Unknown Source)
at java.lang.Integer.parseInt(Unknown Source)
at org.apache.soap.util.net.HTTPUtils.post(Unknown Source)
at org.apache.soap.util.net.HTTPUtils.post(Unknown Source)
at org.apache.soap.transport.http.SOAPHTTPConnection.send(Unknown Source)
at org.apache.soap.rpc.Call.invoke(Unknown Source)
at org.apache.soap.rpc.Call.invoke(Unknown Source)
at
de.mc.etnbestterm.data.SoapCallingDataHolder.callSoaply(SoapCallingDataHolde
r.java:75)
at
de.mc.etnbestterm.data.MainDataHolder.connectServerToDB(MainDataHolder.java:
457)
at de.mc.etnbestterm.data.MainDataHolder.<init>(MainDataHolder.java:61)
at
de.mc.etnbestterm.data.SingletonManager.getMainDataHolder(SingletonManager.j
ava:49)
at de.mc.etnbestterm.gui.WillkommenPanel.jbInit(WillkommenPanel.java:62)
at de.mc.etnbestterm.gui.WillkommenPanel.<init>(WillkommenPanel.java:52)
at de.mc.etnbestterm.gui.MainFrame.<init>(MainFrame.java:40)
at de.mc.etnbestterm.Bestellterminal.jbInit(Bestellterminal.java:67)
at de.mc.etnbestterm.Bestellterminal.<init>(Bestellterminal.java:45)
at de.mc.etnbestterm.Bestellterminal.main(Bestellterminal.java:119)
at java.lang.reflect.Method.invoke(Native Method)
at com.sun.javaws.Launcher.executeApplication(Unknown Source)
at com.sun.javaws.Launcher.executeMainClass(Unknown Source)
at com.sun.javaws.Launcher.continueLaunch(Unknown Source)
at com.sun.javaws.Launcher.handleApplicationDesc(Unknown Source)
at com.sun.javaws.Launcher.handleLaunchFile(Unknown Source)
at com.sun.javaws.Launcher.run(Unknown Source)
at java.lang.Thread.run(Unknown Source)


The customer uses now the hardware firewall "Netscreen" and an ISA Server
2000.

What can I do about it? Is this a bug of SOAP?

thanks in advance

Malte


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira