on 11-29-2006 8:49 PM
We are trying to use SAP Portal Drive (Webdav client) with our Production portal. But, our Production portal is behind TAM, and we have not been able to get SAP Portal Drive to connect through TAM. We set up our Test TAM instance for Basic Auth, and SPD will at least authenticate, but once the explorer for the mapped drive comes up, you cannot see anything and it only shows the IRJ folder, and you can't navigate into it. When I checked the SPD logs, I found that it is sending an OPTIONS request with an XML document in the body. This OPTIONS request is improperly formatted, it dos not include the content-type in the header. Because of this, TAM rejects the request and returns a 400 Bad Request response to SPD. Has anyone experienced this?
Timothy,
My first port-of-call would be to find out why the OPTIONS request does not include the content-type field in the HTTP header (it's a violation of spec: <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec9.html">HTTP/1.1: Method Definitions</a>).
I'd imagine that the reqest is being rejected by TAM because it needs to know the content-type to determine what to do with it...
Regards,
Peter.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
86 | |
10 | |
10 | |
9 | |
6 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.