Please note that VisualCron support is not actively monitoring this community forum. Please use our contact page for contacting the VisualCron support directly.


Guest
2013-09-25T13:24:59Z
We are trying to set up a HTTPS Post task. It relied upon a new feature being brought in during the previous patch, which is done, so thankyou but now we have a new issue.

We needed the content-type header to be "multipart/form-data" and not be changed to match the file type. This is now done but the website is reporting that the file is too large.

According to the support of that website, its because there has been no boundary set in our HTTPS POST request. They also state the boundary is something set by the application sending the POST, so they can't advise on what it should be.

In chat you recommended to add ";boundary=xxxxx" to our content-type header. That didn't work. The file being sent is a zip, but using "multipart/form-data" for the content-type header, what should the boundary be?
Sponsor
Forum information
Support
2013-09-26T02:55:40Z
Boundary can be anything unique.

Basically we use the same code as in this example:

http://stackoverflow.com...post-with-httpwebrequest 

Do you have any .NET programmer in the house that can verify this?
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Guest
2013-09-26T08:26:51Z
Looking at that code, the following as the content-type header should be sufficient:

"multipart/form-data; boundary=---------------------------317205771417341028"

and just in case, i tried it with the two additional dashes as well

"multipart/form-data; boundary=-----------------------------317205771417341028"

But still too large on both attempts. These aren't valid boundaries. Has this new option to not base the content-type header on file type somehow affected the boundaries used in the POST request by VisualCron?
Guest
2013-10-01T16:10:57Z
Hate to bump, but this is still an outstanding issue.
Support
2013-10-02T02:56:40Z
You say it is still "too large". Where do you get this information from?

In the HTTP Task we do not alter anything else than the header you supply. The rest should be taken care of in the background by the .NET component.

I think we need to get a solution (a code snippet) from that you that works so we can see what you think is needed to get this to work. Also, any error messages from the server would be appreciated.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Guest
2013-10-02T15:17:55Z
The "too large" error comes from the website of the regulator we are trying to do the HTTPS Post to. According to their support, the error is automatically given to a post that has no boundary specified.

We don't have any code snippets that do work, we currently do this manually through their website, but wish to automate it, which can be done with a HTTPS Post request.

The best thing we can do at this stage is provide the documentation that the regulator provides, section 4.1 is the part of interest. And all we need to know is can VisualCron fulfill that kind of HTTP Post request.
Support
2013-10-03T19:36:44Z
It is not sure that you can automate it by just knowing the url. It might require something special. I suggest you request a sample for doing this for a large file for let say php or .NET. Once you have that sample we could probably figure out what is needed.
Henrik
Support
http://www.visualcron.com 
Please like  VisualCron on facebook!
Scroll to Top