How to use HTTP Put/Get/Post scripts in Automation tasks? - Progress Community

Loading

Skip to Main Content

How to use HTTP Put/Get/Post scripts in Automation tasks?

The old HTTP scripts in Automation tasks had many limitations, and were developed prior to modern trends in HTTP. They may still work for some simple workflows, but the modern recommendation is to use a custom REST API script to handle the HTTP process instead because this allows administrators to specify additional security and credential settings to connect and transfer the files.

Jan 19, 2023
Knowledge

Title

How to use HTTP Put/Get/Post scripts in Automation tasks?

URL Name

How-to-use-HTTP-Put-Get-Post-scripts-in-Autiomation-tasks

Article Number

000150240

Environment

Product: MOVEit Automation Version: All Supported Versions OS: All Supported Platforms

Question/Problem Description

How to use HTTP Put in a task? Why is a HTTP script failing or erroring in the task?

Potential error messages:
HttpGet: Failed to get file: Error 12003: Error reading data: Could not access server: HTTP return code 401.
Script HTTP Get returned error 12003: Error reading data: Could not access server: HTTP return code 401.
Logging to size 0 err 3700 Script HTTP Get returned error 12003: Error reading data: Could not access server: HTTP return code 401.

Steps to Reproduce

1) Login to Automation with a user that can use scripts in tasks. 2) Create a task with the Source and Destination. 3) Add a Process to use the HTTP Put/Get/Post script 4) Update the script parameters to use the correct path and include credentials if necessary. 5) Save and run the task 6) Encounter the error.

Clarifying Information

These scripts are intended for use with up/downloads to web servers that are NOT MOVEit Transfer servers.

Error Message

In the MoveitC or debug logs: HTTPPost Failed to post file: Error 12003: Error sending data: Could Not Access server" HTTP return code: 405 405 indicates a "Method Not Allowed" error. HttpGet: Failed to get file: Error 12003: Error reading data: Could not access server: HTTP return code 401. Script HTTP Get returned error 12003: Error reading data: Could not access server: HTTP return code 401. Logging to size 0 err 3700 Script HTTP Get returned error 12003: Error reading data: Could not access server: HTTP return code 401.

Defect Number

Enhancement Number

Cause

These scripts will work only when the website requires either no authentication, or HTTP authentication. Unfortunately, many websites require the user to signon via a web form to authenticate. This script will not support websites like that. Additionally, with the advent of API use in many web servers, these scripts will likely not be able to work properly and will fail with an error.

To enable PUT for the HTTP Put script on a remote webserver running Microsoft IIS 6.0, use IIS Manager on that webserver to enable the WebDAV Web Service Extension, and turn on Write access to the virtual directory.

These scripts are not suitable for files larger than a few dozen megabytes, because it loads the entire file into memory before saving it.

Resolution

The first recommendation for HTTP connections is to develop a REST API script that will handle the workflow and upload as intended, because a custom script in this case will allow more specificity for the web server than these standard generic scripts and it can account for security requirements by the server.

Second, please see the documentation about these standard HTTP scripts available in the Common Applications section of the documentation: HTTP Uploads and Downloads - https://docs.progress.com/bundle/moveit-automation-web-admin-help-2025/page/HTTP-Uploads-and-Downloads.html

"HTTP Put" uploads a file to a website, using HTTP[S] with the PUT verb. Note that PUT is not the usual way to upload files, and is not accepted by many websites. The HTTP Post script may work as an alternative for these sites. However, when available, the HTTP PUT technique is preferable because it is simpler.

Use the HTTP Put and Post scripts like a destination, as a per-file process. Typically you would use these in a task with one or more sources.

Workaround

Organizations licensed with ASx modules also have tested using AS2 to allow HTTPS transfers, which may be an option in some scenarios. For more information on AS2 hosts, see this documentation: The AS2 Protocol - https://docs.progress.com/bundle/moveit-automation-web-admin-help-2025/page/The-AS2-Protocol.html

In one case, the issue was resolved by deleting and recreating the task. In this case, there was probably some data that was messed up in the configuration information. Deleting and recreating the task, cleared the issue,

Notes

Keyword Phrase

Last Modified Date

10/6/2025 7:36 PM

Drop Files

Upload FilesOr drop files

Disclaimer

The origins of the information on this site may be internal or external to Progress Software Corporation (“Progress”). Progress Software Corporation makes all reasonable efforts to verify this information. However, the information provided is for your information only. Progress Software Corporation makes no explicit or implied claims to the validity of this information.

Any sample code provided on this site is not supported under any Progress support program or service. The sample code is provided on an "AS IS" basis. Progress makes no warranties, express or implied, and disclaims all implied warranties including, without limitation, the implied warranties of merchantability or of fitness for a particular purpose. The entire risk arising out of the use or performance of the sample code is borne by the user. In no event shall Progress, its employees, or anyone else involved in the creation, production, or delivery of the code be liable for any damages whatsoever (including, without limitation, damages for loss of business profits, business interruption, loss of business information, or other pecuniary loss) arising out of the use of or inability to use the sample code, even if Progress has been advised of the possibility of such damages.

Loading

How to use HTTP Put/Get/Post scripts in Automation tasks? - Progress Community