You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Thomas Peuss (JIRA)" <ji...@apache.org> on 2008/03/04 09:37:50 UTC
[jira] Created: (SOLR-496) Expires HTTP header not set correctly
Expires HTTP header not set correctly
-------------------------------------
Key: SOLR-496
URL: https://issues.apache.org/jira/browse/SOLR-496
Project: Solr
Issue Type: Bug
Components: search
Affects Versions: 1.3
Reporter: Thomas Peuss
I am testing the code from SOLR-127. I have seen following behaviour for the _Expires_ HTTP header.
Solr-config:
{noformat}
<httpCaching lastModFrom="dirLastMod" etagSeed="IBX20080304">
<cacheControl>max-age=2419200</cacheControl>
</httpCaching>
{noformat}
Generated HTTP-headers:
HTTP/1.x 200 OK
Server: Apache-Coyote/1.1
Cache-Control: max-age=2419200
*Expires: Mon, 11 Feb 2008 15:24:49 GMT*
Last-Modified: Fri, 29 Feb 2008 14:25:07 GMT
Etag: "NmVmZmNiYzdjODgwMDAwMElCWDIwMDgwMzA0"
Content-Type: text/xml;charset=UTF-8
Transfer-Encoding: chunked
Content-Encoding: gzip
Vary: Accept-Encoding
*Date: Tue, 04 Mar 2008 08:27:36 GMT*
We are going back in time. max-age=2419200 is 4 weeks in seconds. I checked the code and I have not found anything that could trigger that behaviour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (SOLR-496) Expires HTTP header not set correctly
Posted by "Hoss Man (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man resolved SOLR-496.
---------------------------
Resolution: Fixed
Fix Version/s: 1.3
Assignee: Hoss Man
thanx for catching this Thomas.
Committed revision 634072.
> Expires HTTP header not set correctly
> -------------------------------------
>
> Key: SOLR-496
> URL: https://issues.apache.org/jira/browse/SOLR-496
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.3
> Reporter: Thomas Peuss
> Assignee: Hoss Man
> Fix For: 1.3
>
> Attachments: SOLR-496.patch
>
>
> I am testing the code from SOLR-127. I have seen following behaviour for the _Expires_ HTTP header.
> Solr-config:
> {noformat}
> <httpCaching lastModFrom="dirLastMod" etagSeed="IBX20080304">
> <cacheControl>max-age=2419200</cacheControl>
> </httpCaching>
> {noformat}
> Generated HTTP-headers:
> HTTP/1.x 200 OK
> Server: Apache-Coyote/1.1
> Cache-Control: max-age=2419200
> *Expires: Mon, 11 Feb 2008 15:24:49 GMT*
> Last-Modified: Fri, 29 Feb 2008 14:25:07 GMT
> Etag: "NmVmZmNiYzdjODgwMDAwMElCWDIwMDgwMzA0"
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Content-Encoding: gzip
> Vary: Accept-Encoding
> *Date: Tue, 04 Mar 2008 08:27:36 GMT*
> We are going back in time. max-age=2419200 is 4 weeks in seconds. I checked the code and I have not found anything that could trigger that behaviour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (SOLR-496) Expires HTTP header not set correctly
Posted by "Thomas Peuss (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/SOLR-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Peuss updated SOLR-496:
------------------------------
Attachment: SOLR-496.patch
I have found the problem. And _Integer_ can not hold that long values. I changed the maxAge field to _Long_. It works for my installation with the patch applied.
> Expires HTTP header not set correctly
> -------------------------------------
>
> Key: SOLR-496
> URL: https://issues.apache.org/jira/browse/SOLR-496
> Project: Solr
> Issue Type: Bug
> Components: search
> Affects Versions: 1.3
> Reporter: Thomas Peuss
> Attachments: SOLR-496.patch
>
>
> I am testing the code from SOLR-127. I have seen following behaviour for the _Expires_ HTTP header.
> Solr-config:
> {noformat}
> <httpCaching lastModFrom="dirLastMod" etagSeed="IBX20080304">
> <cacheControl>max-age=2419200</cacheControl>
> </httpCaching>
> {noformat}
> Generated HTTP-headers:
> HTTP/1.x 200 OK
> Server: Apache-Coyote/1.1
> Cache-Control: max-age=2419200
> *Expires: Mon, 11 Feb 2008 15:24:49 GMT*
> Last-Modified: Fri, 29 Feb 2008 14:25:07 GMT
> Etag: "NmVmZmNiYzdjODgwMDAwMElCWDIwMDgwMzA0"
> Content-Type: text/xml;charset=UTF-8
> Transfer-Encoding: chunked
> Content-Encoding: gzip
> Vary: Accept-Encoding
> *Date: Tue, 04 Mar 2008 08:27:36 GMT*
> We are going back in time. max-age=2419200 is 4 weeks in seconds. I checked the code and I have not found anything that could trigger that behaviour.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.