[DAS2] Re: New problem with content-type header in DAS/2 server responses!

[Chervitz, Steve]

I just updated the spec accordingly. Be sure to re-load your browser:

http://biodas.org/documents/das2/das2_get.html

Steve


> From: Allen Day <allenday at ucla.edu>
> Date: Sat, 29 Oct 2005 08:54:59 -0700 (PDT)
> To: "Helt,Gregg" <Gregg_Helt at affymetrix.com>
> Cc: Steve Chervitz <steve_chervitz at affymetrix.com>
> Subject: Re: New problem with content-type header in DAS/2 server responses!
> 
> Looks like the cache server.  FYI, I have updated the server to use all
> "text/xml" Content-Type for all xml response types.  This was approved by
> Lincoln so that web browsers could be pointed at the das server and "just
> work".  I thought these changes had already made their way into the spec,
> but apparently not.
> 
> The table below summarizes what the server should be giving back.  The
> left column shows the command and format request, and the right side shows
> the response Content-Type.
> 
>                     'das/das2xml'             => 'text/xml',
>                     'domain/das2xml'          => 'text/xml',
>                     'domain/compact'          => 'text/plain',
>                     'feature/das2xml'         => 'text/xml',
>                     'feature/chain'           => 'text/plain', #LOOK
>                     'property/das2xml'        => 'text/xml',
>                     'region/das2xml'          => 'text/xml',
>                     'region/compact'          => 'text/plain',
>                     'sequence/das2xml'        => 'text/plain', #LOOK
>                     'sequence/fasta'          => 'text/plain',
>                     'source/das2xml'          => 'text/xml',
>                     'source/compact'          => 'text/plain',
>                     'type/das2xml'            => 'text/xml',
>                     'type/compact'            => 'text/plain',
>                     'type/obo'                => 'text/plain',
>                     'type/rdf'                => 'text/xml',
>                     'versionedsource/das2xml' => 'text/xml',
> 
> As you can see, the text/plain response to the /feature command is NOT
> being given by the server, but somehow being mangled by the cache.  Is
> this going to severly impact your demo?  If so I can disable the cache
> module.  It will be slow though.  An alternative to the cache would be to
> use our squid proxy.  Brian can probably set you up to use it very
> quickly.
> 
> Let me know what needs to be done ASAP.
> 
> -Allen
> 
> 
> On Fri, 28 Oct 2005, Helt,Gregg wrote:
> 
>> I just tried accessing the biopackages DAS/2 server from IGB, with this
>> query:
>> 
>> http://das.biopackages.net/das/genome/human/17/feature?overlaps=chr21/26
>> 027736:26068042;type=SO:mRNA
>> 
>> and I'm getting back a message where the XML looks fine but here are the
>> headers:
>> 
>> HTTP/1.1 200 OK
>> Date: Sat, 29 Oct 2005 05:49:46 GMT
>> Server: Apache/2.0.51 (Fedora)
>> X-DAS-Status: 200
>> Warning: 113 Heuristic expiration
>> Content-Type: text/plain; charset=UTF-8
>> Age: 259582
>> Content-Length: 6004
>> Keep-Alive: timeout=15, max=100
>> Connection: Keep-Alive
>> 
>> But according to the spec the content type header needs to be:
>> Content-Type: text/x-das-features+xml
>> I'm using this in the IGB DAS/2 client to parse responses based on the
>> content type.  With "text/plain; charset=UTF-8" IGB doesn't know what
>> parser to use and gives up.  So right now I can't visualize annotations
>> from the biopackages server.  I'm pretty sure the server was setting the
>> content-type header correctly on Wednesday -- did anything change since
>> then that could be causing this?  Could the server-side cache be doing
>> this for some reason?
>> 
>> Thanks,
>> Gregg
>>  
>>