Re: File size >= 2GB not uploaded in application [Tomcat 7.0.54 Struts: 2.3.24 JAVA: openJDK 1.7.79]
Dear Christopher,
Thanks for your guidelines, we have big hope from Apache Tomcat Team to solve
this problem as this is show stopper for our application, we have also raise
this question on various forum like stack overflow and other,but no relevant
reply till now.
Hope you understand my situation,
please refer the below stackoverflow reference for more detail about this
issue.
http://stackoverflow.com/questions/34783438/dofilter-fails-to-get-any-request-for-the-file-upload-2gb?noredirect=1#comment57315528_34783438
for more information:
-No error are printed in tomcat logs.
- how to configure "call HttpServletRequest.getHeader("Content-Length") as a
String and parse it yourself."
From: Christopher Schultz
Sent: Thursday, January 14, 2016 8:43 PM
To: Tomcat Users List
Subject: Re: File size >= 2GB not uploaded in application [Tomcat 7.0.54
Struts: 2.3.24 JAVA: openJDK 1.7.79]
André,
On 1/14/16 5:02 AM, André Warnier (tomcat) wrote:
> I have not followed this thread in details, but did you check this :
>
> http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributes
> --> maxPostSize
+1
> The maximum size in bytes of the POST which will be handled by the
> container FORM URL parameter parsing. The limit can be disabled by
> setting this attribute to a value less than zero. If not specified, this
> attribute is set to 2097152 (2 megabytes). Note that the
> FailedRequestFilter can be used to reject requests that exceed this limit.
>
> Note: the size above might relate to the *encoded* size of the file, as
> it is transmitted over the WWW (possibly encoded as Base64 e.g.), which
> may mean that an original 1 MB file translates to more than 1 MB bytes
> while being uploaded.
>
> Note also : maybe "Struts" is setting this to some other default value..
>
> Another question : did you check the Tomcat logs ?
IIRC, Tomcat doesn't log anything in these cases. You have to use the
FailedRequestFilter to detect and report the condition. I wouldn't use
that Filter in productio, but it would be good as a simple test to see
if this is the error that is occurring.
When Tomcat refuses to allow a file upload that it too large, it simply
does not parse the parameters, but the request continues to process as
usual (but the servlet doesn't end up getting any of the parameters).
I'm surprised that Struts isn't getting the request in these cases.
-chris
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat 8 Application dispatcherServlet Stats
Theo, On 1/14/16 5:53 AM, Theo Sweeny wrote: > Hello Kyohei, > > -Original Message- > From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com] > Sent: 14 January 2016 09:59 > To: Tomcat Users List > Subject: Re: Tomcat 8 Application dispatcherServlet Stats > > What does "response time" mean? > > The "Processing time" include a time that is from the end of service method > of servlet instance until the end of StandardWrapperValve#invoke(). > > > 2016-01-14 17:27 GMT+09:00 Theo Sweeny : > >> Hello Kyohei, >> >> -Original Message- >> From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com] >> Sent: 14 January 2016 06:45 >> To: Tomcat Users List >> Subject: Re: Tomcat 8 Application dispatcherServlet Stats >> >> Hello >> >> The "Processing time" metric represents the execution time of >> StandardWrapperValve#invoke(). >> This is the execution time of the servlet and filters. >> This value of "Processing time" is the total time of each request >> execution time. >> >> What is the dispatcherServlet? >> If dispatcherServlet accept all request as a front controller(like >> Spring's DispatcherServlet), then this value is the total execution >> time of all request that the context receive. >> >> >> 2016-01-13 20:19 GMT+09:00 Theo Sweeny : >> >>> Hello - at the moment stats can be found for Tomcat 8 web services >>> using the manager UI /manager/status/all >>> >>> Is the "Processing time" metric found under dispatcherServlet [ / ] >>> subsection, the total time take to serve all requests, including the >>> response time for each request? >>> >>> Regards, >>> >>> Theo >> >> Does the total execution time for each request include the response time? >> >> Thank you, >> >> Theo >> > > I think indirectly you have answered my question. From a network > perspective you have the initial connection time to send the request > (request time), then you have the time to process the request, and > finally response time back to the client. Both the processing time > and response time for the purpose of this task are merged under the > umbrella of response time. So going full circle - the > dispatcherServlet Processing time fits the bill of response time. There is a case where this might not actually give you what you are looking for -- which sounds essentially like the amount of time the server spent processing that request. If StandardWrapperValve only times how long invoke() takes and (and I haven't read the code, so I'm not sure) some component in Tomcat executes *after* invoke() completes for the purposes of flushing any buffered data back to the client, then "Processing Time" may be off by the amount of time it takes Tomcat to flush those buffers back to the client. If you have big buffers or slow clients, this could add up quickly. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: File size >= 2GB not uploaded in application [Tomcat 7.0.54 Struts: 2.3.24 JAVA: openJDK 1.7.79]
André, On 1/14/16 5:02 AM, André Warnier (tomcat) wrote: > I have not followed this thread in details, but did you check this : > > http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributes > --> maxPostSize +1 > The maximum size in bytes of the POST which will be handled by the > container FORM URL parameter parsing. The limit can be disabled by > setting this attribute to a value less than zero. If not specified, this > attribute is set to 2097152 (2 megabytes). Note that the > FailedRequestFilter can be used to reject requests that exceed this limit. > > Note: the size above might relate to the *encoded* size of the file, as > it is transmitted over the WWW (possibly encoded as Base64 e.g.), which > may mean that an original 1 MB file translates to more than 1 MB bytes > while being uploaded. > > Note also : maybe "Struts" is setting this to some other default value.. > > Another question : did you check the Tomcat logs ? IIRC, Tomcat doesn't log anything in these cases. You have to use the FailedRequestFilter to detect and report the condition. I wouldn't use that Filter in productio, but it would be good as a simple test to see if this is the error that is occurring. When Tomcat refuses to allow a file upload that it too large, it simply does not parse the parameters, but the request continues to process as usual (but the servlet doesn't end up getting any of the parameters). I'm surprised that Struts isn't getting the request in these cases. -chris - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Poodle attack and RC4 cipher complain, even after disabling SSLv3 in tomcat and Apache.
2016-01-14 13:27 GMT+03:00 Weare Borg : > Hello friends, > > I recently scanned our domain Qualys SSL lab and found out that we have 2 > problems as listed below : > > 1) This server is vulnerable to the POODLE attack. If possible, disable SSL > 3 to mitigate. Grade capped to C > 2) This server accepts RC4 cipher, but only with older protocol versions. > Grade capped to B. > > Our server runs Debian X64 with Apache 2.2 as a load-balancer and fail-over > for 2 tomcat instances. So I configured the settings for both Apache and > Tomcat for both these problems. Here are the changes I made, but I still > keep getting the two errors I mentioned above. What am I doing wrong? > > Changes to mods-available/ssl.conf : > > SSLProtocol All -SSLv2 -SSLv3 > SSLHonorCipherOrder on > SSLCipherSuite ALL:!ADH:!RC4:+HIGH:+MEDIUM:!LOW:!SSLv2:!SSLv3!EXPORT You are missing ":" between SSLv3 and EXPORT. So actually you are not disabling SSLv3. > Changes to 8443 connector for TOmcat : > > > protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" >> maxThreads="200" compression="off" How do you proxy your requests? Usually requests are proxied with AJP protocol, so the above HTTP connector configuration does not matter. Best regards, Konstantin Kolinko - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 8 Application dispatcherServlet Stats
Hello Kyohei, -Original Message- From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com] Sent: 14 January 2016 09:59 To: Tomcat Users List Subject: Re: Tomcat 8 Application dispatcherServlet Stats What does "response time" mean? The "Processing time" include a time that is from the end of service method of servlet instance until the end of StandardWrapperValve#invoke(). 2016-01-14 17:27 GMT+09:00 Theo Sweeny : > Hello Kyohei, > > -Original Message- > From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com] > Sent: 14 January 2016 06:45 > To: Tomcat Users List > Subject: Re: Tomcat 8 Application dispatcherServlet Stats > > Hello > > The "Processing time" metric represents the execution time of > StandardWrapperValve#invoke(). > This is the execution time of the servlet and filters. > This value of "Processing time" is the total time of each request > execution time. > > What is the dispatcherServlet? > If dispatcherServlet accept all request as a front controller(like > Spring's DispatcherServlet), then this value is the total execution > time of all request that the context receive. > > > 2016-01-13 20:19 GMT+09:00 Theo Sweeny : > > > Hello - at the moment stats can be found for Tomcat 8 web services > > using the manager UI /manager/status/all > > > > Is the "Processing time" metric found under dispatcherServlet [ / ] > > subsection, the total time take to serve all requests, including the > > response time for each request? > > > > Regards, > > > > Theo > > Does the total execution time for each request include the response time? > > Thank you, > > Theo > I think indirectly you have answered my question. From a network perspective you have the initial connection time to send the request (request time), then you have the time to process the request, and finally response time back to the client. Both the processing time and response time for the purpose of this task are merged under the umbrella of response time. So going full circle - the dispatcherServlet Processing time fits the bill of response time. Thanks for the help! Theo Avios Group (AGL) Ltd is a limited company registered in England (registered number 2260073 and VAT number 512566754) whose registered address is Astral Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group (AGL) Limited is part of the IAG group of companies This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
Poodle attack and RC4 cipher complain, even after disabling SSLv3 in tomcat and Apache.
Hello friends, I recently scanned our domain Qualys SSL lab and found out that we have 2 problems as listed below : 1) This server is vulnerable to the POODLE attack. If possible, disable SSL 3 to mitigate. Grade capped to C 2) This server accepts RC4 cipher, but only with older protocol versions. Grade capped to B. Our server runs Debian X64 with Apache 2.2 as a load-balancer and fail-over for 2 tomcat instances. So I configured the settings for both Apache and Tomcat for both these problems. Here are the changes I made, but I still keep getting the two errors I mentioned above. What am I doing wrong? Changes to mods-available/ssl.conf : SSLProtocol All -SSLv2 -SSLv3 SSLHonorCipherOrder on SSLCipherSuite ALL:!ADH:!RC4:+HIGH:+MEDIUM:!LOW:!SSLv2:!SSLv3!EXPORT Changes to 8443 connector for TOmcat : protocol="org.apache.coyote.http11.Http11NioProtocol" SSLEnabled="true" > maxThreads="200" compression="off" > sslEnabledProtocols="TLSv1.2,TLSv1.1,TLSv1" > ciphers="TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256, > TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA384, > TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_RC4_128_SHA, > TLS_RSA_WITH_AES_128_CBC_SHA256,TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA256, > TLS_RSA_WITH_AES_256_CBC_SHA,SSL_RSA_WITH_RC4_128_SHA" > compressionMinSize="1024" scheme="https" secure="true" clientAuth="false" > sslProtocol="TLS" > keystoreFile="/path/to/file.keystore" > keystorePass="PASSWORD" URIEncoding="utf-8"/> > I would really like to use compression, but because the links I found suggested to disable compression, I have disabled them. Can I use compression with SSL disabled, how are they both related? Still, I keep getting the above 2 errors. What am I missing? If any more information is required, kindly let me know…Kindly let me know. Thank you,.
Re: File size >= 2GB not uploaded in application [Tomcat 7.0.54 Struts: 2.3.24 JAVA: openJDK 1.7.79]
Hi.
I have not followed this thread in details, but did you check this :
http://tomcat.apache.org/tomcat-7.0-doc/config/http.html#Common_Attributes
--> maxPostSize
The maximum size in bytes of the POST which will be handled by the container FORM URL
parameter parsing. The limit can be disabled by setting this attribute to a value less
than zero. If not specified, this attribute is set to 2097152 (2 megabytes). Note that the
FailedRequestFilter can be used to reject requests that exceed this limit.
Note: the size above might relate to the *encoded* size of the file, as it is transmitted
over the WWW (possibly encoded as Base64 e.g.), which may mean that an original 1 MB file
translates to more than 1 MB bytes while being uploaded.
Note also : maybe "Struts" is setting this to some other default value..
Another question : did you check the Tomcat logs ?
On 14.01.2016 10:52, Rahul Singh wrote:
Hello Christopher ,
Thanks for your input,
ServletRequest.getContentLength is declared to return an int value (32-bit):
* Integer.MAX_VALUE = 2^31 - 1 = 2147483647
* 2GiB = 2 * 1024 * 1024 * 1024 = 2147483648
* 2147483648 > 2147483647
Therefore, request.getContentLength cannot be used to fetch
content-lengths over 2GiB - 1byte.
Yes above is already investigated, BTW thanks .
You have to use
ServletRequest.getContentLengthLong (new in servlet 3.1)
for this we have to upgrade tomcat 8, currently we are using tomcat 7.0.54.
or call
HttpServletRequest.getHeader("Content-Length") as a String and parse it
yourself.
OK, but where we need to do this, in init() method or in doFilter() method, but
FYI, the request(upload file >2GB) is not reached to doFilter().
Apart from above thread we want to share more information so that tomcat team
help us to get out from this issue.
For my struts project the doFilter() fails to get any request from the file
upload form in cases the size of the file is greater than 2gb.
Below is the code fragment:
Filter is as follows:
public void doFilter(ServletRequest req, ServletResponse res, FilterChain
chain) throws IOException, ServletException
{
HttpServletRequest request = (HttpServletRequest) req;
HttpServletResponse response = (HttpServletResponse) res;
HttpSession session = request.getSession(false);
request.setCharacterEncoding("UTF-8");
/*
do the other business work example request response monitoring and
logging
*/
chain.doFilter(request, response);
}
jsp is :
For my jsp the form is submitted as a XMLHttpRequest via the underlying
javascipt.
Now when I upload a a file (lesser than 2gb) ,in my dofilter() method I have
checked the uri and request length for the request.
They are as expected via the action called in the jsp form and the file size.
The file upload works fine in this case. But in case where the file size is
greater than 2gb ,
in my doFilter() method no request is available for the file upload action
called by the form submit(for file size greater than 2 gb).
Thus the upload does not proceed further in such cases.
I am using servlet 3.0.
What do I need to do to support larger than 2 gb file uploads, so that the
request reaches the doFilter() method?
From: Christopher Schultz
Sent: Wednesday, January 13, 2016 8:11 PM
To: Tomcat Users List
Subject: Re: File size >= 2GB not uploaded in application [Tomcat 7.0.54
Struts: 2.3.24 JAVA: openJDK 1.7.79]
Rahul,
On 1/12/16 10:56 PM, Rahul Singh wrote:
Hi,
Define "Not successful"? Exceptions thrown? File truncated? Upload
never starts? Never finishes?
Not successful :
Request Never finishes, we have trace the HttpServlet request object
and request.getContentLength return 0 in case when file size is >=2GB,
No exception thrown, as well as when file size is less than 2GB, then
request.getContentLength return the correct value of file size in
byte.
ServletRequest.getContentLength is declared to return an int value (32-bit):
* Integer.MAX_VALUE = 2^31 - 1 = 2147483647
* 2GiB = 2 * 1024 * 1024 * 1024 = 2147483648
* 2147483648 > 2147483647
Therefore, request.getContentLength cannot be used to fetch
content-lengths over 2GiB - 1byte. You have to use
ServletRequest.getContentLengthLong (new in servlet 3.1) or call
HttpServletRequest.getHeader("Content-Length") as a String and parse it
yourself.
-chris
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h..
Re: Tomcat 8 Application dispatcherServlet Stats
What does "response time" mean? The "Processing time" include a time that is from the end of service method of servlet instance until the end of StandardWrapperValve#invoke(). 2016-01-14 17:27 GMT+09:00 Theo Sweeny : > Hello Kyohei, > > -Original Message- > From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com] > Sent: 14 January 2016 06:45 > To: Tomcat Users List > Subject: Re: Tomcat 8 Application dispatcherServlet Stats > > Hello > > The "Processing time" metric represents the execution time of > StandardWrapperValve#invoke(). > This is the execution time of the servlet and filters. > This value of "Processing time" is the total time of each request > execution time. > > What is the dispatcherServlet? > If dispatcherServlet accept all request as a front controller(like > Spring's DispatcherServlet), then this value is the total execution time of > all request that the context receive. > > > 2016-01-13 20:19 GMT+09:00 Theo Sweeny : > > > Hello - at the moment stats can be found for Tomcat 8 web services > > using the manager UI /manager/status/all > > > > Is the "Processing time" metric found under dispatcherServlet [ / ] > > subsection, the total time take to serve all requests, including the > > response time for each request? > > > > Regards, > > > > Theo > > Avios Group (AGL) Ltd is a limited company registered in England > > (registered number 2260073 and VAT number 512566754) whose registered > > address is Astral Towers, Betts Way, London Road, Crawley, West Sussex > > RH10 9XY . Avios Group (AGL) Limited is part of the IAG group of > > companies This email and any files transmitted with it are > > confidential and intended solely for the use of the individual or entity > to whom they are addressed. > > If you have received this email in error please notify the system > manager. > > > > Does the total execution time for each request include the response time? > > Thank you, > > Theo > > Avios Group (AGL) Ltd is a limited company registered in England > (registered number 2260073 and VAT number 512566754) whose registered > address is Astral Towers, Betts Way, London Road, Crawley, West Sussex RH10 > 9XY . Avios Group (AGL) Limited is part of the IAG group of companies This > email and any files transmitted with it are confidential and intended > solely for the use of the individual or entity to whom they are addressed. > If you have received this email in error please notify the system manager. >
Re: File size >= 2GB not uploaded in application [Tomcat 7.0.54 Struts: 2.3.24 JAVA: openJDK 1.7.79]
Hello Christopher ,
Thanks for your input,
>ServletRequest.getContentLength is declared to return an int value (32-bit):
>* Integer.MAX_VALUE = 2^31 - 1 = 2147483647
>* 2GiB = 2 * 1024 * 1024 * 1024 = 2147483648
>* 2147483648 > 2147483647
>Therefore, request.getContentLength cannot be used to fetch
>content-lengths over 2GiB - 1byte.
Yes above is already investigated, BTW thanks .
You have to use
>ServletRequest.getContentLengthLong (new in servlet 3.1)
for this we have to upgrade tomcat 8, currently we are using tomcat 7.0.54.
> or call
>HttpServletRequest.getHeader("Content-Length") as a String and parse it
>yourself.
OK, but where we need to do this, in init() method or in doFilter() method, but
FYI, the request(upload file >2GB) is not reached to doFilter().
Apart from above thread we want to share more information so that tomcat team
help us to get out from this issue.
For my struts project the doFilter() fails to get any request from the file
upload form in cases the size of the file is greater than 2gb.
Below is the code fragment:
Filter is as follows:
public void doFilter(ServletRequest req, ServletResponse res, FilterChain
chain) throws IOException, ServletException
{
HttpServletRequest request = (HttpServletRequest) req;
HttpServletResponse response = (HttpServletResponse) res;
HttpSession session = request.getSession(false);
request.setCharacterEncoding("UTF-8");
/*
do the other business work example request response monitoring and
logging
*/
chain.doFilter(request, response);
}
jsp is :
For my jsp the form is submitted as a XMLHttpRequest via the underlying
javascipt.
Now when I upload a a file (lesser than 2gb) ,in my dofilter() method I have
checked the uri and request length for the request.
They are as expected via the action called in the jsp form and the file size.
The file upload works fine in this case. But in case where the file size is
greater than 2gb ,
in my doFilter() method no request is available for the file upload action
called by the form submit(for file size greater than 2 gb).
Thus the upload does not proceed further in such cases.
I am using servlet 3.0.
What do I need to do to support larger than 2 gb file uploads, so that the
request reaches the doFilter() method?
From: Christopher Schultz
Sent: Wednesday, January 13, 2016 8:11 PM
To: Tomcat Users List
Subject: Re: File size >= 2GB not uploaded in application [Tomcat 7.0.54
Struts: 2.3.24 JAVA: openJDK 1.7.79]
Rahul,
On 1/12/16 10:56 PM, Rahul Singh wrote:
> Hi,
>
>> Define "Not successful"? Exceptions thrown? File truncated? Upload
>> never starts? Never finishes?
>
> Not successful :
>
> Request Never finishes, we have trace the HttpServlet request object
> and request.getContentLength return 0 in case when file size is >=2GB,
>
> No exception thrown, as well as when file size is less than 2GB, then
> request.getContentLength return the correct value of file size in
> byte.
ServletRequest.getContentLength is declared to return an int value (32-bit):
* Integer.MAX_VALUE = 2^31 - 1 = 2147483647
* 2GiB = 2 * 1024 * 1024 * 1024 = 2147483648
* 2147483648 > 2147483647
Therefore, request.getContentLength cannot be used to fetch
content-lengths over 2GiB - 1byte. You have to use
ServletRequest.getContentLengthLong (new in servlet 3.1) or call
HttpServletRequest.getHeader("Content-Length") as a String and parse it
yourself.
-chris
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
RE: Tomcat 8 Application dispatcherServlet Stats
Hello Kyohei, -Original Message- From: Kyohei Nakamura [mailto:nakamura.kyohei@gmail.com] Sent: 14 January 2016 06:45 To: Tomcat Users List Subject: Re: Tomcat 8 Application dispatcherServlet Stats Hello The "Processing time" metric represents the execution time of StandardWrapperValve#invoke(). This is the execution time of the servlet and filters. This value of "Processing time" is the total time of each request execution time. What is the dispatcherServlet? If dispatcherServlet accept all request as a front controller(like Spring's DispatcherServlet), then this value is the total execution time of all request that the context receive. 2016-01-13 20:19 GMT+09:00 Theo Sweeny : > Hello - at the moment stats can be found for Tomcat 8 web services > using the manager UI /manager/status/all > > Is the "Processing time" metric found under dispatcherServlet [ / ] > subsection, the total time take to serve all requests, including the > response time for each request? > > Regards, > > Theo > Avios Group (AGL) Ltd is a limited company registered in England > (registered number 2260073 and VAT number 512566754) whose registered > address is Astral Towers, Betts Way, London Road, Crawley, West Sussex > RH10 9XY . Avios Group (AGL) Limited is part of the IAG group of > companies This email and any files transmitted with it are > confidential and intended solely for the use of the individual or entity to > whom they are addressed. > If you have received this email in error please notify the system manager. > Does the total execution time for each request include the response time? Thank you, Theo Avios Group (AGL) Ltd is a limited company registered in England (registered number 2260073 and VAT number 512566754) whose registered address is Astral Towers, Betts Way, London Road, Crawley, West Sussex RH10 9XY . Avios Group (AGL) Limited is part of the IAG group of companies This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager.
