VMware {code} Community
tos2k
Expert
Expert

Https file download issues VC/ESX

Hi!

I am experiencing troubles when dowloading files via https:/<vc>/folder feature via VC - files and folders can not be accessed/download (404 - not found) when the path contains paranthesis?

Does someone know

1) a reason for this behaviour

2) a workaround (escape characters?)

? If someone can confirm this, I will create a SR at VMware.

Tos2k

0 Kudos
3 Replies
tos2k
Expert
Expert

VMware has confirmed that this is a known bug!

The bug is especially nerving on ESXi hosts: VMware adds paranthesis by default :smileyalert: to datastores with same names. As the the only way to up and download files on ESXi servers is http(s) based, this will make it impossible then.

Consider that one (or more) parantheses in one place at the whole url to a files will break the up/download. The url in general contains the datacenter, datastore and sub directories, so this is quiet imortant (no fix for it within the last two months anyway...)

Tos2k

p.s. Dont use paranthesis in VMware environments, ever!

0 Kudos
shar_234
Contributor
Contributor

Hi

I note the same issue of getting status code 404(Not found) when the URLs have the character ":" in the datastore name.

Is there some SR raised for this issue. If yes pls forward the SR reference # to me.

One more ques. abt the Http file upload.

Is there an upper limit on the number of httpClient connections that can be established with the ESXi host?

We notice "ReadTimeOut" Socket exception thrown whenever there are more than 4-5 connections

opened for http file transfer.

Awaiting reply...

Thanks and Regards

Saradha

0 Kudos
tos2k
Expert
Expert

Hi!

I dont know the SR# of SR concerning other non-working characters in http://<esx/vc>/folder urls

I dont know the original SR# of SR concerning other "(" and ")" in http://<esx/vc>/folder urls, just my own. On this SR I got the informations that VMware was aware of this. I cannot find any information around this in the release notes anyway...

What I realized is that VC stops answering request, in general, if it has to handle a count of around 100 sessions.

Indeed i had to find a workaround for this: You can "steel" the session cookie from your original Vim Session and use it for authorization on http(s) file up- and download VC too. This avoids creating new sessions on VC.

Tos2k

0 Kudos