topic Re: http 301 moved permanently error in Talend Studio

http 301 moved permanently error

Anonymous — Mon, 20 May 2019 20:19:32 GMT

I have an error on the following URL:

https://us19.api.mailchimp.com/export/1.0/list?apikey=sxxxxxx&id=ea772398be&since=2019-05-19 00:00:00

I have x'ed out the apikey. The url works fine in Postman so I know that it is not the URL. I am using a tRestClient.

Re: http 301 moved permanently error

nfz11 — Tue, 21 May 2019 03:58:08 GMT

Did you try ticking 'Follow redirects' in the tRestClient?

This is a simple GET without any headers or parameters other than what you show in the query, right?

You could look at the Postman console and details of the request and response in Postman to make sure you are doing the same thing in Talend.

Re: http 301 moved permanently error

Anonymous — Tue, 21 May 2019 15:32:30 GMT

I tried the redirect. I got a different error. See attachment.

Starting job EMS_PGA_AUDIENCE_Tags_Copy at 07:43 21/05/2019.

[statistics] connecting to socket on port 3858
[statistics] connected
SLF4J: Class path contains multiple SLF4J bindings.
SLF4J: Found binding in [jar:file:/C:/Talend/Talend-Studio-20181026_1147-V7.1.1/configuration/.m2/repository/org/talend/libraries/slf4j-log4j12-1.7.2/6.0.0/slf4j-log4j12-1.7.2-6.0.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: Found binding in [jar:file:/C:/Talend/Talend-Studio-20181026_1147-V7.1.1/configuration/.m2/repository/org/talend/libraries/slf4j-log4j12-1.7.5/6.0.0/slf4j-log4j12-1.7.5-6.0.0.jar!/org/slf4j/impl/StaticLoggerBinder.class]
SLF4J: See for an explanation.SLF4J: Actual binding is of t

To see the whole post, download it here
OriginalPost.pdf

Re: http 301 moved permanently error

NGuittet — Tue, 14 Mar 2023 10:23:00 GMT

Hello,

Has this question been resolved ?

I have a same issue, and here is what I can say about it.

The "Follow redirects" option on the tHTTPClient component seem to forget the "Authorization" header when it builds the new request at the URL provided by the "Location" header.

Indeed, I tried this in Talend API Tester, and it works well there if I run the request with following the redirects.

However, when I reproduce the exact same request in a Talend Job with a tHTTPClient, I only get a HTTP 401 Unauthorized response.

Also, When I tick the "Log messages" option, the redirections are not showned in the Studio Console. So I cannot see by where the bounces went, and which headers were sent...

Did anyone observed such a behavior ?

Thanks & Regards

Nicolas

Re: http 301 moved permanently error

WTree — Mon, 13 Nov 2023 08:22:21 GMT

did you find any solution? I have the same issue.

Re: http 301 moved permanently error

NGuittet — Mon, 13 Nov 2023 08:35:09 GMT

Hi WTree,

What I understand is that this os somewhat a design behavior, so that a malicious URL inserted in the middle of a series of redirect wouldn't get your credentials.

For my part, I fixed it by providing the exact final URL to the authentication request.

Regards,

Nicolas