POST problems with IIS Plugin

Question

I am using the latest version of the IIS plugin for Weblogic (build: Apr 14 2002
17:53:13)
It seems that the ISAPI Filter (iisforward.dll) does not forward all http POSTs
- however it does seem to work fine for http GET's.
We have configured the plugin (you will see the attached debug dump) to forward
all calls on "/weblogic". If we perform http GET's on such a URL (using IE) everything
works fine - and the call is routed to Weblogic.
When we make a SOAP call using our C++ client, (a http POST) through the IIS plugin
we get a 405 error. If we artificially add the ".wlforward" extension on the context
URL (in our C++ client ) then it is forwarded correctly to weblogic by the Application
Extension (iisproxy.dll) - so the problem lies with the ISAPI filter. Also, if
we remove the ISAPI filter from IIS, we get the same 405 error - which confirms
that the ISAPI filter is not catching the POST's.
More puzzling, however, is that the SOAP requests from our Java SOAP client (using
WLS SOAP) works fine.
The problem must have something to do with the difference in structure of the
POSTS.
Normally, I would attach the logs/config in a zip file - but that seems broken
at the moment. Instead they are all pasted in below.....
-Nick
Successful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
Host: localhost:8080
Connection: Keep-Alive
Content-Length: 1965
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Authorization: Basic c3lzdGVtOnBhc3N3b3Jk
UNSuccessful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
SOAPAction: ""
Content-Type: text/xml
Connection: close
Content-Length: 1670
IIS 405 Response:
HTTP/1.1 405 Method not allowed
Server: Microsoft-IIS/5.0
Date: Thu, 25 Jul 2002 14:28:52 GMT
Allow: OPTIONS, TRACE, GET, HEAD
Content-Length: 3126
Content-Type: text/html
IIS Plugin Config:
Properties loaded from path: 'D:\Inetpub\WeblogicPlugin\iisproxy.ini'
Query String: '__WebLogicBridgeConfig'
General Server List:
Host: 'localhost' Port: 7001 Status: OK
ConnectRetrySecs: '2'
ConnectTimeoutSecs: '10'
CookieName: 'JSESSIONID'
Debug: '12'
DebugConfigInfo: 'ON'
DefaultFileName: ''
DynamicServerList: 'ON'
ErrorPage: ''
FileCaching: 'ON'
HungServerRecoverSecs: '300'
Idempotent: 'OFF'
KeepAliveEnabled: 'ON'
KeepAliveSecs: '30'
PathPrepend: ''
PathTrim: '/weblogic'
MaxSkips: '10'
MaxPostSize: '-1'
SecureProxy: 'OFF'
WLLogFile: 'D:\Inetpub\WeblogicPlugin\iisPlugin.log'
WLProxySSL: 'OFF'
Runtime statistics:
requests: 1
successful requests: 1
Exception objects created: 0
Exception Objects deleted: 0
URL Objects created: 1
URL Objects deleted: 1
connections recycled: 0
UNKNOWN_ERROR_CODE exceptions: 0
CONNECTION_REFUSED exceptions: 0
CONNECTION_TIMEOUT exceptions: 0
READ_ERROR exceptions: 0
WRITE_ERROR exceptions: 0
READ_TIMEOUT exceptions: 0
WRITE_TIMEOUT exceptions: 0
UNKNOWN_HOST exceptions: 0
NO_RESOURCES exceptions: 0
PROTOCOL_ERROR exceptions: 0
CONFIG_ERROR exceptions: 0
FAILOVER_REQUIRED exceptions: 0
Build date/time: Apr 14 2002 17:53:13

Answer 1

Doh. :< I hope you can get someone here from the BEA guys/gals to help out.
I'm outside of my league at this point. Sorry about that. Good luck.
"Nick Minutello" <[email protected]> wrote
in message news:[email protected]...
>
>
Thanks.
Sadly, my IIS configuration is correct. The plugin seems to work fine if Ijust
use my browser (http GET) for either forward-by-extension (*.jsp) orforward-by-path
(/weblogic/*).
However, there seems to be a problem when I use SOAP (http POST). For somereason,
when I use my C++ SOAP client (using WASP), then the ISAPI filter (the onethat
generates the .wlforward on the URL) doesnt modify the URL - hence the403...
If I use my java client.... everything is fine. Comparing the two httppackets,
I dont see anything obviously wrong - but something is making the WLSplugin choke.
>
Cheers,
Nick
"PHenry" <[RemoveBeforeSending][email protected]> wrote:
Howdy. I had a similar problem. I'm not a BEA support person, but maybe
I
might be able to help. If not, at least someone's listening. :>
Did you add the .jsp AND the .wlforward in the path redirection under
your
web app in IIS? I read the instructions thoroughly (or so I thought),
and I
wasn't able to get the POST to work. :< But as I reread the
instructions,
I
had put in the .jsp (is it under Home Directory, Configuration I think?),
and I put in the ISAPI dll, but I didn't put in the .wlforward (in with
the
..jsp). Once I did that, and restarted the box, all was good! :>
That might help. And if not, at least one of the BEA people have one
less
thing to try. Good luck.
"Nick Minutello" <[email protected]>
wrote
in message news:[email protected]...
I am using the latest version of the IIS plugin for Weblogic (build:Apr
14 2002
17:53:13)
It seems that the ISAPI Filter (iisforward.dll) does not forward allhttp
POSTs
- however it does seem to work fine for http GET's.
We have configured the plugin (you will see the attached debug dump)to
forward
all calls on "/weblogic". If we perform http GET's on such a URL (usingIE) everything
works fine - and the call is routed to Weblogic.
When we make a SOAP call using our C++ client, (a http POST) throughthe
IIS plugin
we get a 405 error. If we artificially add the ".wlforward" extensionon
the context
URL (in our C++ client ) then it is forwarded correctly to weblogicby the
Application
Extension (iisproxy.dll) - so the problem lies with the ISAPI filter.Also, if
we remove the ISAPI filter from IIS, we get the same 405 error -which
confirms
that the ISAPI filter is not catching the POST's.
More puzzling, however, is that the SOAP requests from our Java SOAPclient (using
WLS SOAP) works fine.
The problem must have something to do with the difference in structureof
the
POSTS.
Normally, I would attach the logs/config in a zip file - but that seemsbroken
at the moment. Instead they are all pasted in below.....
-Nick
Successful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
Host: localhost:8080
Connection: Keep-Alive
Content-Length: 1965
Content-Type: text/xml; charset=utf-8
SOAPAction: ""
Authorization: Basic c3lzdGVtOnBhc3N3b3Jk
UNSuccessful POST http header:
POST /weblogic/webservice/BondInstrumentService HTTP/1.0
SOAPAction: ""
Content-Type: text/xml
Connection: close
Content-Length: 1670
IIS 405 Response:
HTTP/1.1 405 Method not allowed
Server: Microsoft-IIS/5.0
Date: Thu, 25 Jul 2002 14:28:52 GMT
Allow: OPTIONS, TRACE, GET, HEAD
Content-Length: 3126
Content-Type: text/html
IIS Plugin Config:
Properties loaded from path: 'D:\Inetpub\WeblogicPlugin\iisproxy.ini'
Query String: '__WebLogicBridgeConfig'
General Server List:
Host: 'localhost' Port: 7001 Status: OK
ConnectRetrySecs: '2'
ConnectTimeoutSecs: '10'
CookieName: 'JSESSIONID'
Debug: '12'
DebugConfigInfo: 'ON'
DefaultFileName: ''
DynamicServerList: 'ON'
ErrorPage: ''
FileCaching: 'ON'
HungServerRecoverSecs: '300'
Idempotent: 'OFF'
KeepAliveEnabled: 'ON'
KeepAliveSecs: '30'
PathPrepend: ''
PathTrim: '/weblogic'
MaxSkips: '10'
MaxPostSize: '-1'
SecureProxy: 'OFF'
WLLogFile: 'D:\Inetpub\WeblogicPlugin\iisPlugin.log'
WLProxySSL: 'OFF'
Runtime statistics:
requests: 1
successful requests: 1
Exception objects created: 0
Exception Objects deleted: 0
URL Objects created: 1
URL Objects deleted: 1
connections recycled: 0
UNKNOWN_ERROR_CODE exceptions: 0
CONNECTION_REFUSED exceptions: 0
CONNECTION_TIMEOUT exceptions: 0
READ_ERROR exceptions: 0
WRITE_ERROR exceptions: 0
READ_TIMEOUT exceptions: 0
WRITE_TIMEOUT exceptions: 0
UNKNOWN_HOST exceptions: 0
NO_RESOURCES exceptions: 0
PROTOCOL_ERROR exceptions: 0
CONFIG_ERROR exceptions: 0
FAILOVER_REQUIRED exceptions: 0
Build date/time: Apr 14 2002 17:53:13