Spurious "Invalid cookie header" warnings about airtable.java

[joesondow]

So now doing it this way you get the data from airtable using .select()? I don't know what I am doing wrong but I can update, remove, and create new records in airtable but I can't seem to get them unless I use find.

This question seems out of scope for this issue ticket. I recommend asking in the Airtable community forums or on Stack Overflow. Or for an example of how I've used .select() successfully you can check one of my projects here.

[ArturoGJ]

Im having the same problem, did you find a solution?

[joesondow]

The workaround I used was this. I added two logging libraries to my projects in build.gradle:

dependencies {
    ... 

    // Provides a logger implementation for airtable.java to get rid of warning
    compile group: 'org.slf4j', name: 'slf4j-simple', version: '1.7.25'

    // Use log4j logging to be able to turn off spurious warnings from libraries
    compile group: 'log4j', name: 'log4j', version: '1.2.17'

    ...
}

and I put this in src/main/resources/log4j.properties

# Root logger option
log4j.rootLogger=INFO, stdout

# Direct log messages to stdout
log4j.appender.stdout=org.apache.log4j.ConsoleAppender
log4j.appender.stdout.Target=System.out
log4j.appender.stdout.layout=org.apache.log4j.PatternLayout
log4j.appender.stdout.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n

# Remove spurious cookie headers warning
log4j.logger.org.apache.http.client.protocol.ResponseProcessCookies=FATAL

[ArturoGJ]

So now doing it this way you get the data from airtable using .select()? I don't know what I am doing wrong but I can update, remove, and create new records in airtable but I can't seem to get them unless I use find. El mié., 14 de agosto de 2019 1:33, Joe Sondow <[email protected]> escribió:

…

I added two logging libraries to my projects in build.gradle: dependencies { ... // Provides a logger implementation for airtable.java to get rid of warning compile group: 'org.slf4j', name: 'slf4j-simple', version: '1.7.25' // Use log4j logging to be able to turn off spurious warnings from libraries compile group: 'log4j', name: 'log4j', version: '1.2.17' ... } and I put this in src/main/resources/log4j.properties # Root logger option log4j.rootLogger=INFO, stdout # Direct log messages to stdout log4j.appender.stdout=org.apache.log4j.ConsoleAppender log4j.appender.stdout.Target=System.out log4j.appender.stdout.layout=org.apache.log4j.PatternLayout log4j.appender.stdout.layout.ConversionPattern=%d{yyyy-MM-dd HH:mm:ss} %-5p %c{1}:%L - %m%n # Remove spurious cookie headers warning log4j.logger.org.apache.http.client.protocol.ResponseProcessCookies=FATAL — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#35?email_source=notifications&email_token=AGLCDWR5UPK3M2HIXMQLSWDQEORNHA5CNFSM4G7ZOR42YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4H2S6I#issuecomment-521120121>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AGLCDWRWSDLHRZYXUEYKQ7TQEORNHANCNFSM4G7ZOR4Q> .

[fstuff]

According to the posts here https://stackoverflow.com/questions/36473478/fixing-httpclient-warning-invalid-expires-attribute-using-fluent-api
this is an issue that originates in the Apache HTTP client. There is a proposed solution of setting the cookie spec to "standard":
HttpClient httpClient = HttpClients.custom() .setDefaultRequestConfig(RequestConfig.custom() .setCookieSpec(CookieSpecs.STANDARD).build()) .build();

[joesondow]

There's a good looking list of solutions to this problem based on which library and which syntax is used to create the Http Client on this page: https://www.lenar.io/invalid-cookie-header-invalid-expires-attribute/

[joesondow]

It looks like airtable.java uses Unirest for http calls. Unirest updated in 2019 to fix this error.

Kong/unirest-java#97

I've attempted to figure out all the necessary changes in pull request #52 but the integration tests are a challenge for an outsider to run, so I'm not sure if I missed anything.