Sun Web Server &
I am trying to setup a document directory on Sun Web Server 7. I am able to create them using the local drive but when I try to point to a network share it does not work.
I am able to manually connect from the web server to that network share.
I am running the Web server with the Domain Administrator account.
Both the Web server and the server with the network share are Windows 2003 Adv Server.
I get the following error in the web server log file:
[22/Nov/2006:15:42:51] warning ( 5100): for host 130.170.94.12 trying to GET /test7, uri-clean reports: HTTP4131: not full path: \\crwd0004\GRPDATA
[636 byte] By [
RussellJD] at [2007-11-26 11:40:35]
# 1
It's probably just a simple problem of Web Server finding backslashes where it expected forward slashes. Web Server expects UNC path names to begin with //, not \\.
How did you configure this document directory? Did you use the Admin Console GUI, the wadm CLI, or did you manually edit configuration files? (I think the GUI and CLI should have handled the \\ to // conversion for you automatically. If they didn't, that's a bug.)
# 2
I originally configured the document directory throught the Admin console.. I also tried manually editing the obj.conf file as follows but I still could not get it to work.NameTrans fn="pfx2dir" from="/test7" dir="\\\\crwd0004\\GRPDATA"Thanks,
# 4
elving,I gave that a try and still no luck. I get this error in the log file now:[27/Nov/2006:15:01:33] warning ( 4652): for host 130.170.94.12 trying to GET /test7, uri-clean reports: CORE4393: malformed path: //crwd0004/GRPDATAAny other Ideas?Thanks,
# 5
It looks like this is a bug in Web Server 7.0. The nt-uri-clean SAF will always reject UNC paths.
I think the only work around is to avoid using nt-uri-clean. Unfortunately, nt-uri-clean performs some important checks on the requested URI. If you're not concerned about aliasing (i.e. if you don't have any URI-based or path-based ACLs and aren't worried about clients being able to retrieve the source code for dynamic content on your server), you can comment out the PathCheck fn="nt-uri-clean" line in the obj.conf configuration file.
I'm sorry it took so long for me to get back to you.
# 6
elving,
I tried that work around and it works. You are correct in that it does present a security risk.
I know Web Server 7 hasn't been officially released yet.
Do you know what the process is to get this bug addressed? Do I need to open up a case?
We are looking to migrate from Microsoft's IIS to Sun's Web Server 7 so this type of virtual directory would be a requirement for us to move forward.
I appreciate your time and effort in looking into this.
Thanks,
# 7
If you have a Sun support contract, you can open a case. There's already a bug report open against the issue, CR 6334248. In your case, you can say that you want to escalate CR 6334248 in 7.0.
I'm sure this bug will be fixed eventually. Unfortunately, I don't yet know when.
A safer work around might be to make the PathCheck fn="nt-uri-clean" directive conditional. For example:<If $uri =~ './/' or $uri =~ '\.\.' or $uri =~ '\.$' or $uri =~ '\./' or $uri =~ '~'>
PathCheck fn="nt-uri-clean"
</If>
