-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix the AccessLoggingFilter #12
Comments
I have created a new version of the AccessLoggingFilter (with the same name) which does the following: o Does NOT wrap the HTTP response to count the bytes actually transferred, in case this is the source of the problem The new filter also does the following: o Retrieves the size of the input file from the HTTP response "Content-Length" (same as the TDS does) |
This has been tested successfully at JPL after loading 356452 entries in the esgf_node_manager.access_logging table. But is is possible that problems arise only for large database tables and high concurrency situations. |
Example of entry for restricted download: select user_id, url, remote_addr, user_agent, service_type, batch_update_time, to_timestamp(date_fetched), success, duration, user_idp, data_size, xfer_size, duration from esgf_node_manager.access_logging order by date_fetched desc limit 1; |
Who: Luca
It has been reported that in a small percentage of the cases, data downloads are not completed successfully because of the AccessLoogingFilter. What is wrong in the AccessLoggingFilter is unknown.
The text was updated successfully, but these errors were encountered: