tFileFetch used to retrieve cookie, acces denied

[Anonymous]

Hi,
I want to save a cookie (for authentification) by using tFileFetch for use with another tFileFetch (if subjobOK with the first tFileFecth) but it doesn't work.
Error message :
connecting to socket on port 3589
connected
Exception in component tFileFetch_1
java.io.FileNotFoundException: C:\Temp\Cookie (Accès refusé)
I'm using WinXP with Admin rights. The directory "C:\Temp\Cookie" exist.
Any idea on this ?

[Anonymous]

Hi
Welcome to Talend Community!
It indicates that you don't have the right to access temp directory.
Please check it again. Or change directory.
Regards,
Pedro

[Anonymous]

Hi Pedro,
In File Explorer, I have full access to all directories.
I changed the directory (project workspace, Windows, ...), the problem is the same.
A tFileTouch on the same directory works.
What do you think ?

[Anonymous]

Hi
Which version of TOS do you use?
Could you show me the URL?
I need to reproduce it first.
Regards,
Pedro

[Anonymous]

I use TOS for Data Integration 5.1.1 on WinXP Pro with Admin rights.
The URL is an Intranet website
When I uncheck "Save cookie", the response header is good :
connecting to socket on port 3865
connected
Status Line: HTTP/1.1 200 OK
*** Response Header ***
Date: Thu, 07 Jun 2012 09:54:20 GMT
Server: Apache
Content-Length: 4059
Content-Type: text/html;charset=ISO-8859-1
disconnected

[Anonymous]

Having the same issue -- from other posts, it looks like this is a result of a bug with how cookies are handled. Is there a workaround? Is it on the roadmap to be fixed? I am on TIS 5.1.2.

[_AnonymousUser]

In the german translation it says "Cookie Verzeichnis" which equals "cookie directory". According to the sourcecode a file is loaded - not a directory at the hdd!
Directory means: A File with cookies (a directory of cookies in a file) - you give the filename of the directory-file.
Took me an hour to get this
lol

[Anonymous]

@pr014m3r2 -- not sure if you'll check back on this topic since it appears you are a guest, but curious if you actually successfully used the feature. I find that the only thing that gets written is a nonsensical 4 byte file. From observing the content that should actually be written using developer tools in chrome, there is definitely different detailed information in the actual cookie that is sent and should be persisted. I've tried every kind of variation I can think of in Talend to see if the results might vary, but no luck.

[cterenzi]

This is an old thread, but I ran into the same issue.  Opening the code view revealed that the cookie saving code expected a file name in the "Cookie directory" field.  If provided with a directory, it fails, but if given a file name in the target path it will write the cookie(s) to that file.
Ex: "C:/Talend/cookies" fails with a FileNotFoundException but "C:/Talend/cookies/cookie.txt" succeeds.