WebDAV and WebNS on 11503

[mike.harlow]

I've having problems getting web authoring thru our CSS11503 running WebNS 7.x

I've come across this comment about ACNS

[Quote] In ACNS software, HTTP request methods are categorized as supported and unsupported. HTTP 1.1 request methods (for example, GET, HEAD, or POST) are supported by default. Nonstandard request methods, such as Web-Based Distributed Authoring and Versioning (WebDAV) are not [End-Quote]

Is there a problem with WebNS passing my WebDAV traffic onto the servers? Can this be fixed? They are demanding the removal of the CSS if they cannot get their WebDav working.

Thanks.

[Gilles Dufour]

If you are using a layer 5 content rule, we indeed only support POST,GET.

So, if you have the command 'url ...' in the content rule, you will have problem with other HTTP method.

Solution is to remove the 'url ...' command to make the rule layer 3 or layer 4.

Future releases should correct this problem.

[But this is not soon]

Regards,

Gilles.

[mike.harlow]

Hi. My services look like this:

service Vista-1-80

port 80

protocol tcp

keepalive type http

ip address 192.168.144.3

keepalive uri "/webct/about.jsp"

active

service Vista-2-80

port 80

protocol tcp

keepalive type http

ip address 192.168.144.4

keepalive uri "/webct/about.jsp"

active

And the content:

content HTTP-80

add service Vista-1-80

add service Vista-2-80

protocol tcp

port 80

balance aca

vip address A.B.1.27

advanced-balance arrowpoint-cookie

active

Am I doing layer 5? or layer 4? I dont have any content rules, I just want to balance based on load/availability.

[Gilles Dufour]

Layer 5 because of the advanced balance arrowpoint coookie.

Since you apparently need some form of stickyness but can't use layer 5 rule, I would suggest sitcky source ip.

Regards,

Gilles.

[mike.harlow]

Thanks Gillies.

Can you suggest how I might do this? The CSS was unpacked and put into production within hours of arrival, without time to experiment or learn. I got it going by using someone elses configuration as a starting point. I dont know that much about the CSS features, and I cannot fiddle with it easily. I have a telephone conference in a few hours with the Project Manager, Application developers (from USA), and the Solaris Server Admin to work out what options we have.

The application is an online learning system (Vista/WebCT), using port 80 and eventually 443 (the CSS has the SSL module already). It also has a chat system on port 2304, and they want to be able to WebDAV to port 80 as well. I need to balance the traffic across the backend server nodes evenly, and be sticky so that a student remains connected to the same node for their session which may last several hours. Source IP stickiness sounds like a possibility. Can you provide me more details?

Thanks, Michael

[Gilles Dufour · Accepted solution]

all you need is to go to your content rule with port 80 and enter the command 'advanced-balance sticky-srcip' or something similar.

Regards,

Gilles.