• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE


  • Subject: Re: Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE
  • From: Aaron Rosenzweig <email@hidden>
  • Date: Fri, 09 May 2014 22:15:32 -0400

Hi Hugi,

Yes, this is a known problem with the WO api. You cannot patch it… like we have done with NSArray in the past to get generics support. “Patching” means making another .java class with the same package name and loading it before Apple’s… 

In this case, patching won’t cure it because we need a “long” instead of an “integer” and there are several places where this API would have to change.

The simple answer is to live with the 2GB limit.

The longer answer… only by rewriting WO can you get around this, like TB is trying to do.
Aaron Rosenzweig / Chat 'n Bike
e:  email@hidden  t:  (301) 956-2319
Chat 'n Bike Chat 'n Bike

On May 8, 2014, at 5:15 AM, Hugi Thordarson <email@hidden> wrote:

Thanks, but it’s not that. Apache handles large files just fine, so the problem seems to be with the WO adaptor.

Cheers,
- hugi



On 8.5.2014, at 09:09, Þór Sigurðsson <email@hidden> wrote:

Rebuild Apache with:
-DLARGEFILE_SOURCE -DFILE_OFFSET_BITS=64

And you'll be rollin'

Með kveðju,
Þór Sigurðsson
Tölvunarfræðingur - Forritari
Sími: 480-6000

<image001.png>

Samgöngustofa - www.samgongustofa.is
Umferðarstofa, Borgartúni 30, 105 Reykjavík

On 8.5.2014, at 08:49, Hugi Thordarson <email@hidden> wrote:

Hi all

I’m attempting to stream a ~3GB file from a WO app. When I DirectConnect to the app, the content-length header is correctly set to “3371573248”, but if the response goes through the Apache adaptor (CentOS 5.5/Apache 2.2), the content-length header is changed to “2147483647” (Integer.MAX_VALUE), resulting in a truncated file for most clients.

I just attempted to install the most recent compiled Wonder adaptor from wocommunity org, but it doesn’t solve the problem.

Anyone familiar with this?

Cheers,
- hugi
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:

This email sent to email@hidden




Fyrirvari á tölvupósti / e-mail disclaimer
http://samgongustofa.is/fyrirvari/
Do not post admin requests to the list. They will be ignored. Webobjects-dev mailing list (email@hidden) Help/Unsubscribe/Update your Subscription: This email sent to email@hidden
  • Follow-Ups:
    • Re: Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE
      • From: Hugi Thordarson <email@hidden>
References: 
 >Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE (From: Hugi Thordarson <email@hidden>)
 >Re: Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE (From: Hugi Thordarson <email@hidden>)

  • Prev by Date: Re: Starting second instance=app not available
  • Next by Date: advice on inheritance??
  • Previous by thread: Re: Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE
  • Next by thread: Re: Large response: Apache adaptor changing content-length header to Integer.MAX_VALUE
  • Index(es):
    • Date
    • Thread