Transfer File via HTTP POST?

Post any question you may have in regards to GoAnywhere Director and let our talented support staff and other users assist you.
16 posts Page 2 of 2

alexben14

Posts: 7
Joined: Fri Apr 24, 2015 4:29 pm

Post by alexben14 » Thu Jun 11, 2015 2:31 pm
Thanks Rick, here is the XML Job and attached is the log.
Code: Select all
<project name="HTTPS Push" mainModule="Main" version="2.0">
	<description>This will Push a file to a HTTPS server using HTTP Post method.</description>

	<module name="Main" logLevel="debug">

		<https resourceId="${RemoteSource}" version="1.0">
			<post uri="${DestinationPath}${fileName}">
				<file name="${fileName}" path="${SourcePath}${fileName}" />
			</post>
		</https>

	</module>
</project>
Attachments
1400701194171.log
Job Log with Debug Flag.
(18.85 KiB) Downloaded 336 times

Support_Rick

Support Specialist
Posts: 592
Joined: Tue Jul 17, 2012 2:12 pm
Location: Phoenix, AZ

Post by Support_Rick » Thu Jun 11, 2015 2:44 pm
Alex,

Please review your URI. The attached Error
Code: Select all
6/10/15 4:44:08 PM            INFO      The request made to '/sde/alert/FNS0ACS2/upload/CA_20150610-alert_daily.dat' completed with the status 'HTTP/1.1 404 Not Found'
6/10/15 4:44:08 PM            DEBUG     Closing connection
6/10/15 4:44:08 PM            DEBUG     Connection closed
6/10/15 4:44:08 PM            ERROR     404 Not Found
6/10/15 4:44:08 PM            INFO      Finished project 'HTTPS Push'
6/10/15 4:44:08 PM            ERROR     404 Not Found
Indicates that it can't find that path/filename on the target system. Thus, the 404 Not Found message.
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696

alexben14

Posts: 7
Joined: Fri Apr 24, 2015 4:29 pm

Post by alexben14 » Thu Jun 11, 2015 2:52 pm
I have reviewed the URI and the path exists. The file should not exits because it is a new file, so it should be uploaded to the folder with that name. Do I need to do something with that ?

Support_Rick

Support Specialist
Posts: 592
Joined: Tue Jul 17, 2012 2:12 pm
Location: Phoenix, AZ

Post by Support_Rick » Thu Jun 11, 2015 3:03 pm
Try something like this instead ...
Code: Select all
<https resourceId="${RemoteSource}" version="1.0">
   <post uri="${DestinationPath}">
      <file name="${fileName}" path="${SourcePath}${fileName}" />
   </post>
</https>
Usually "name" is a value like "file" or "filename". It depends on what the prompted value on the https interface gives you. SourcePath & FileName should provide the Path and Name of the file that you're wanting to Post to that location in "DestinationPath"
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696

alexben14

Posts: 7
Joined: Fri Apr 24, 2015 4:29 pm

Post by alexben14 » Thu Jun 11, 2015 3:15 pm
It is replying me with the same error of 404 Not Found. Really weird I think.

Support_Rick

Support Specialist
Posts: 592
Joined: Tue Jul 17, 2012 2:12 pm
Location: Phoenix, AZ

Post by Support_Rick » Thu Jun 11, 2015 4:44 pm
Can you send the updated Job Log run with Debug Mode Enabled?
Rick Elliott
Lead Solutions Consultant
(402) 944.4242
(800) 949-4696
16 posts Page 2 of 2