Thanks for your reply Scott.
Thank you for confirming that it seems to be the remote end that is closing the connection and not an error from the sending end.
I have just tested the same file transfer using geturi and receive the exact same broken pipe error.
At the moment I do not have access to ...
Search found 31 matches
- Thu Jan 23, 2025 8:21 am
- Forum: HTTPAPI
- Topic: HTTPAPIR4 gsk_secure_soc_write rc=406 issue
- Replies: 2
- Views: 26036
- Thu Jan 23, 2025 2:08 am
- Forum: HTTPAPI
- Topic: HTTPAPIR4 gsk_secure_soc_write rc=406 issue
- Replies: 2
- Views: 26036
HTTPAPIR4 gsk_secure_soc_write rc=406 issue
We are using HTTPAPIR4 to upload a backup file to Azure.
We have enabled large file support and successfully uploaded files that are 3-5 GB
But a larger file is failing with the error (GSKit) I/O: Broken pipe.
To eliminate the size of the debug file being an issue we turned off debug in HTTPAPIR4 ...
We have enabled large file support and successfully uploaded files that are 3-5 GB
But a larger file is failing with the error (GSKit) I/O: Broken pipe.
To eliminate the size of the debug file being an issue we turned off debug in HTTPAPIR4 ...
- Thu Jan 16, 2025 4:32 am
- Forum: HTTPAPI
- Topic: Object is too large to process
- Replies: 10
- Views: 61460
Re: Object is too large to process
I am having issues sending a large file and it was suggested to increase the size being sent on each call to sendraw2. sendraw2 is a copy of sendraw modified for files > 2GB
sendraw has wwBuf set to 8192 - I was looking to change this to 32768 to see if the larger size would make any difference ...
sendraw has wwBuf set to 8192 - I was looking to change this to 32768 to see if the larger size would make any difference ...
- Wed Nov 27, 2024 1:00 am
- Forum: HTTPAPI
- Topic: BOM at start of IFS stream file
- Replies: 4
- Views: 33720
Re: BOM at start of IFS stream file
Thanks Scott,
I am going by the advise of others that is is a Byte Order Mark but Mr Google seems to agree.
I am saying that when I try and do an XML-INTO that it fails with invalid XML as it does not like the first three bytes.
If we run the same request in Postman we do not get the BOM.
We have ...
I am going by the advise of others that is is a Byte Order Mark but Mr Google seems to agree.
I am saying that when I try and do an XML-INTO that it fails with invalid XML as it does not like the first three bytes.
If we run the same request in Postman we do not get the BOM.
We have ...
- Thu Nov 21, 2024 2:20 am
- Forum: HTTPAPI
- Topic: BOM at start of IFS stream file
- Replies: 4
- Views: 33720
BOM at start of IFS stream file
We are using httpapir4 procedure http_req to retrieve a list from Azure.
This list is returned in xml format.
The file is saved to the IFS
The first 3 characters are invalid for xml
Is there a way to not get these characters.
This is the first part of the stream file - <?xml version="1.0 ...
This list is returned in xml format.
The file is saved to the IFS
The first 3 characters are invalid for xml
Is there a way to not get these characters.
This is the first part of the stream file - <?xml version="1.0 ...
- Mon Nov 11, 2024 5:17 am
- Forum: HTTPAPI
- Topic: Object is too large to process
- Replies: 10
- Views: 61460
Re: Object is too large to process
You don't need to do anything with chunking, it will work as-is. And it isn't something you enable. If the server sends data that is chunked, HTTPAPI must handle it. If it doesn't, HTTPAPI has to handle it without chunking.
We are using PUT not GET. Wouldn't the use of chunking be part of sending ...
We are using PUT not GET. Wouldn't the use of chunking be part of sending ...
- Mon Nov 11, 2024 3:48 am
- Forum: HTTPAPI
- Topic: Object is too large to process
- Replies: 10
- Views: 61460
Re: Object is too large to process
Would it be easier for me to just make the mods?
Depends on the answer to my previous question on how to enable large file support.
It appears at a first glance the parameters for the xxx64 version of the API's are very similar just larger size.
So if you have time and would like to do the mods ...
Depends on the answer to my previous question on how to enable large file support.
It appears at a first glance the parameters for the xxx64 version of the API's are very similar just larger size.
So if you have time and would like to do the mods ...
- Mon Nov 11, 2024 3:43 am
- Forum: HTTPAPI
- Topic: Object is too large to process
- Replies: 10
- Views: 61460
Re: Object is too large to process
You should be thanking Peder. I am only reading this for the first time now.
Apologies Peder, I should read who the response was from.
Thank you for your assistance.
Not clear what you mean, here. Is something wrong with the chunking in HTTPAPI that you need to change it?
I don't expect there ...
Apologies Peder, I should read who the response was from.
Thank you for your assistance.
Not clear what you mean, here. Is something wrong with the chunking in HTTPAPI that you need to change it?
I don't expect there ...
- Fri Nov 08, 2024 8:22 am
- Forum: HTTPAPI
- Topic: Object is too large to process
- Replies: 10
- Views: 61460
Re: Object is too large to process
Thank you Scott.
We are still progressing and found stat64() and will review open64()
However I am still looking for an example of chunking as at the current I am struggling on how to do this.
We needed to introduce stat64() and a larger field size for the size of the file which requires a ...
We are still progressing and found stat64() and will review open64()
However I am still looking for an example of chunking as at the current I am struggling on how to do this.
We needed to introduce stat64() and a larger field size for the size of the file which requires a ...
- Wed Nov 06, 2024 3:27 am
- Forum: HTTPAPI
- Topic: Object is too large to process
- Replies: 10
- Views: 61460
Object is too large to process
I am trying to transfer a large file and receiving an error that the file is too large.
We are using
rc = http_req( 'PUT'
: wrkurl
: rcvFile
: *OMIT
: sndFile
: *OMIT );
In debug we see the error occur on the open
In procedure http_req
if %parms >= 5 and %addr(SendStmf) <> *null ...
We are using
rc = http_req( 'PUT'
: wrkurl
: rcvFile
: *OMIT
: sndFile
: *OMIT );
In debug we see the error occur on the open
In procedure http_req
if %parms >= 5 and %addr(SendStmf) <> *null ...