HTTP 411 error(Content length)

Hi @AnotherFraudUser

We are using AF utility extensions specifically to connect to Sharepoint to fetch the files, download them and upload the new ones.

Initial Node to get the access token(Get SP AccessToken) is working fine both on server and locally, but the downstream nodes such as (ListSPfiles, MoveSPFiles, Upload File to SP, Download File from SP) are all failing with 411 error on KNIME Server, which apparently has something to do with the absence of the content-length header in the request.

Do we have any clue about the error and how to fix it? We are using KNIME 4.7.* version of KNIME Executor.

Regards,
Nagarjun S
KNIME Team

3 Likes

Hi @nagarjun36,
will have a look, most likely i missed an issue when migrating the xml parsing to gson.

In the testing I tought i fixed the content length issue. Will have a look and come back to you :slight_smile:

But is it only an issue with the KNIME server or appear locally as well?
Also could you check which version of AF utilities / Knime Server / Executor is used? :slight_smile:

Hi @AnotherFraudUser

Thanks for the reply, Customer is currently using KNIME 4.7.1 version(AP and Executor). Please find the below screenshot showing the AF utilities version.

Please find the detailed report and logs from the customer about which nodes are working and which nodes aren’t working properly.

KNIME-AFUtility-nodes.xlsx (20.4 KB)
executor-create-SP-folder.log (7.7 KB)
executor-list-SP-files.log (6.5 KB)
executor-MS-authentication.log (4.8 KB)

I hope this information helps you in identifying the root cause.

Regards,
Nagarjun S

1 Like

Great thanks for the Infos @nagarjun36
Will try to analyse / get a fix on Thursday evening or latest Friday evening

Hi @AnotherFraudUser ,

Thanks for the update, we look forward for the fix.

Regards,
Nagarjun S

Hi @nagarjun36,

for all content length issues i implemented a workaround.
At least with the local 4.7 instance that should work again (inkl. Checkout/Checkin file and remove folder) :slight_smile:
Please also check and confirm from your side :+1:

For the server issue please also update the extension and test again - but here I have to say cannot test as I currently do not have access to any knime server :see_no_evil:

However the executor-MS-authentication.log does sound like the standard KNIME sharepoint nodes instead of my AF Utilities

1 Like

@nagarjun36 any feedback? :slight_smile:
Does it also work on your/customer side?
Just want to confirm before pushing it to 5.1 as well

1 Like

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.