It appears, at least on my implementation, that gecko uploadify (gu) does not work over an ssl connection. If I am using an ssl connection gu just throws an IO error for eacy/any file you try to upload, and if I turn ssl off it works just fine.
This might just be an issue with my implementation of umbraco but I thought I would throw it out there and see if anyone else ran into this. If not, then I know its my issue and I'll have to dig deeper to figure it out.
To debug this, could you try running fiddler2 during an upload and see if one of the requests results in an error. If yes: what's the error and where does it occur?
Thanks for the fast response. Fiddler2 or charles did not catch any errors in the attempt. It was actually, an issue with my setup, at least it appears that way.
I host multiple website from one umbraco instance and handle the hostnames in umbraco, the site in IIS accepts all traffic on the IP. When I'm builindg out a site I assign the ip address as the host name and work inside of it that way. Apprently using the uploader from the ip doesn't work well. I switched over to a "live" site and used the back office from its dns alias, and it worked just fine, http/https not withstanding.
SSL Issues
It appears, at least on my implementation, that gecko uploadify (gu) does not work over an ssl connection. If I am using an ssl connection gu just throws an IO error for eacy/any file you try to upload, and if I turn ssl off it works just fine.
This might just be an issue with my implementation of umbraco but I thought I would throw it out there and see if anyone else ran into this. If not, then I know its my issue and I'll have to dig deeper to figure it out.
To debug this, could you try running fiddler2 during an upload and see if one of the requests results in an error. If yes: what's the error and where does it occur?
Thanks for the fast response. Fiddler2 or charles did not catch any errors in the attempt. It was actually, an issue with my setup, at least it appears that way.
I host multiple website from one umbraco instance and handle the hostnames in umbraco, the site in IIS accepts all traffic on the IP. When I'm builindg out a site I assign the ip address as the host name and work inside of it that way. Apprently using the uploader from the ip doesn't work well. I switched over to a "live" site and used the back office from its dns alias, and it worked just fine, http/https not withstanding.
So it appears that the issue was my own.
Good to know that it works with SSL, as it should! :-)
is working on a reply...