ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTP Content Expiration

Post new topic  Reply to topic
 HTTP Content Expiration « View previous topic :: View next topic » 
Author Message
smdavies99
PostPosted: Fri Jan 16, 2015 3:53 am    Post subject: HTTP Content Expiration Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

I'm currently trying to understand the following (from a spec)
Quote:

When setting up the HTTP Response for XXX make sure that the HTTP Header includes an expiration time. Otherwise the HTTP message that is sent back to machine that is hosting YYY/Server will live until the machine is rebooted. In our testing environment, we enable the content expiration to expire immediately in Internet Information Services (IIS) as per image below:


They show a panel from an IIS server config where the messages were set to timeout immediately.

In IIS it is called CONTENT EXPIRATION
http://technet.microsoft.com/en-gb/library/cc770661%28v=ws.10%29.aspx

The bits I don't quite get are as follows:-
1) If a message is set to timeout immediately then does this mean in reality 'immediately after is has been received' or something else
2) Can we set this ourselves in a flow?
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jan 16, 2015 4:26 am    Post subject: Re: HTTP Content Expiration Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY

smdavies99 wrote:
I'm currently trying to understand the following (from a spec)
Quote:

When setting up the HTTP Response for XXX make sure that the HTTP Header includes an expiration time. Otherwise the HTTP message that is sent back to machine that is hosting YYY/Server will live until the machine is rebooted. In our testing environment, we enable the content expiration to expire immediately in Internet Information Services (IIS) as per image below:


They show a panel from an IIS server config where the messages were set to timeout immediately.

In IIS it is called CONTENT EXPIRATION
http://technet.microsoft.com/en-gb/library/cc770661%28v=ws.10%29.aspx

The bits I don't quite get are as follows:-
1) If a message is set to timeout immediately then does this mean in reality 'immediately after is has been received' or something else
2) Can we set this ourselves in a flow?


I would expect this to be a specific IIS feature that needs to be set in IIS.

From your description I understood that the content, once received would live in IIS forever until it is expired. I would expect that the setting of the expire upon receipt is being set as an IIS feature.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
mgk
PostPosted: Fri Jan 16, 2015 4:36 am    Post subject: Reply with quote

Padawan

Joined: 31 Jul 2003
Posts: 1638

This is a feature of base HTTP, rather than IIS - see section "14.21" in RFC 2616 about here: https://tools.ietf.org/html/rfc2616#page-127 which talks about the HTTP "Expires" header. This is also mentioned in the first sentence of the TechNet article you mentioned: "Configure the HTTP expires response header when you want to specify the expiration of Web content" although it is easy to miss it.

To set this in an HTTPReply node, simply create an "Expires" field in an "HTTPReplyHeader" parser to the date you want before the HTTPRReply node.

Kind regards,
_________________
MGK
The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
Back to top
View user's profile Send private message
fjb_saper
PostPosted: Fri Jan 16, 2015 4:47 am    Post subject: Reply with quote

Grand High Poobah

Joined: 18 Nov 2003
Posts: 20697
Location: LI,NY

Thanks for setting me straight.
_________________
MQ & Broker admin
Back to top
View user's profile Send private message Send e-mail
smdavies99
PostPosted: Fri Jan 16, 2015 5:05 am    Post subject: Reply with quote

Jedi Council

Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.

Many thanks for the information. I'll be giving it a try later today.


_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995

Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions.
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » HTTP Content Expiration
Jump to:  



You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
Protected by Anti-Spam ACP
 
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.