V2.0.6 Browser caching problems

Hi there,

We seem to have a problem where when we click on links we are getting cached
versions of the pages, and have to hit F5 to refresh (IE 5.5).

Is there some sort of setting within RT (or Apache) we can set to stop this
happening?

Regards,

Derek…

Any views expressed in this message are those of the individual sender,
except where the sender states them to be the views of Foreshore Limited.

This e-mail is intended only for the individual or entity to which it is
addressed and contains information that is private and confidential. If
you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying is strictly prohibited. If you
have received this e-mail in error please delete it immediately and
advise us by return e-mail to hostmaster@foreshore.net

“DF” == Derek Fage derek.fage@foreshore.net writes:

DF> We seem to have a problem where when we click on links we are
DF> getting cached versions of the pages, and have to hit F5 to
DF> refresh (IE 5.5).

This would be a brower bug. It works properly in Netscape and KDE’s
Konqueror. It fails as above in Opera 5 as well, which is annoying
since otherwise Opera is so f*ing fast. Opera seems to just ignore
any no-cache and expires headers. It would seem IE5.5 is doing the
same, which is bad.

| DF> We seem to have a problem where when we click on links we are
| DF> getting cached versions of the pages, and have to hit F5 to
| DF> refresh (IE 5.5).
|
| This would be a brower bug. It works properly in Netscape and KDE’s
±–>8

IE5.5 also has an annoying tendency to “fake” POST operations and instead
return to cached pages; we see this a lot with IE5.5 and RT1. Backlevel to
5.01 if you must use IE.

brandon s. allbery [os/2][linux][solaris][freebsd] allbery@kf8nh.apk.net
system administrator [JAPH][WAY too many hats] allbery@ece.cmu.edu
electrical and computer engineering KF8NH
carnegie mellon university [linux: proof of the million monkeys theory]

Thanks Vivek,

How can I check if I’m actually receiving no-cache and expires headers?

I’ve used www.samspade.org to do an HTTP browse on my site (shows headers),
and there does not appear to be any cache or expires information there.

Derek…-----Original Message-----
From: Vivek Khera [mailto:khera@kcilink.com]
Sent: 06 September 2001 15:23
To: rt-users@lists.fsck.com
Subject: Re: [rt-users] v2.0.6 Browser caching problems

“DF” == Derek Fage derek.fage@foreshore.net writes:

DF> We seem to have a problem where when we click on links we are
DF> getting cached versions of the pages, and have to hit F5 to
DF> refresh (IE 5.5).

This would be a brower bug. It works properly in Netscape and KDE’s
Konqueror. It fails as above in Opera 5 as well, which is annoying
since otherwise Opera is so f*ing fast. Opera seems to just ignore
any no-cache and expires headers. It would seem IE5.5 is doing the
same, which is bad.

rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Any views expressed in this message are those of the individual sender,
except where the sender states them to be the views of Foreshore Limited.

This e-mail is intended only for the individual or entity to which it is
addressed and contains information that is private and confidential. If
you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying is strictly prohibited. If you
have received this e-mail in error please delete it immediately and
advise us by return e-mail to hostmaster@foreshore.net

Hi Derek!

I had the same problem on several webpages I made when IE 5.5 came out.

I solved it in a very simple way: I just send an expiration date with the
http-header which is some years in the past. You can do this with mod_perl
or by putting:

in the HTML-code.

That should fix the problem with IE 5.5, as it forces the browser to reload
the page every time the page is visited.

I hope this helped you solve your problem.

Regards,

Benjamin Boksa

Hi there,

We seem to have a problem where when we click on links we are getting cached
versions of the pages, and have to hit F5 to refresh (IE 5.5).

Is there some sort of setting within RT (or Apache) we can set to stop this
happening?

Regards,

Derek…



Any views expressed in this message are those of the individual sender,
except where the sender states them to be the views of Foreshore Limited.

This e-mail is intended only for the individual or entity to which it is
addressed and contains information that is private and confidential. If
you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying is strictly prohibited. If you
have received this e-mail in error please delete it immediately and
advise us by return e-mail to hostmaster@foreshore.net


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Benjamin Boksa
b.boksa@sidebysite.de

side by site GmbH & Co. KG
Druckgestaltung & Webdesign

Barbarastr. 3-9 (Block 6)
D-50735 Koeln

Telefon: +49 221 2790964
Telefax: +49 221 2790965

http://www.sidebysite.de/

Does perhaps Temporary Internet Files settings of IE solve this by setting
Check for newer versions of stored pages to Every visit to the page?

A.

Benjamin Boksa wrote:

Hi Derek!

I had the same problem on several webpages I made when IE 5.5 came out.

I solved it in a very simple way: I just send an expiration date with the

http-header which is some years in the past. You can do this with mod_perl

or by putting:

<META HTTP-EQUIV=“expires” CONTENT=“Wed, 26 Feb 1997 08:21:57 GMT”>

in the HTML-code.

That should fix the problem with IE 5.5, as it forces the browser to reload

the page every time the page is visited.

I hope this helped you solve your problem.

Regards,

Benjamin Boksa

Hi there,

We seem to have a problem where when we click on links we are getting cached

versions of the pages, and have to hit F5 to refresh (IE 5.5).

Is there some sort of setting within RT (or Apache) we can set to stop this

happening?

Regards,

Derek…

Any views expressed in this message are those of the individual sender,

except where the sender states them to be the views of Foreshore Limited.

This e-mail is intended only for the individual or entity to which it is

addressed and contains information that is private and confidential. If

you are not the intended recipient you are hereby notified that any

dissemination, distribution or copying is strictly prohibited. If you

have received this e-mail in error please delete it immediately and

advise us by return e-mail to hostmaster@foreshore.net

rt-users mailing list

rt-users@lists.fsck.com

http://lists.fsck.com/mailman/listinfo/rt-users


Derek:

Try inserting this line in WebRT/Elements/Header.  If that

makes it better with IE5, I’ll drop this into 2.0.7.

-jOn Thu, Sep 06, 2001 at 05:09:08PM +0200, Benjamin Boksa wrote:

Hi Derek!

I had the same problem on several webpages I made when IE 5.5 came out.

I solved it in a very simple way: I just send an expiration date with the
http-header which is some years in the past. You can do this with mod_perl
or by putting:

in the HTML-code.

That should fix the problem with IE 5.5, as it forces the browser to reload
the page every time the page is visited.

I hope this helped you solve your problem.

Regards,

Benjamin Boksa

Hi there,

We seem to have a problem where when we click on links we are getting cached
versions of the pages, and have to hit F5 to refresh (IE 5.5).

Is there some sort of setting within RT (or Apache) we can set to stop this
happening?

Regards,

Derek…



Any views expressed in this message are those of the individual sender,
except where the sender states them to be the views of Foreshore Limited.

This e-mail is intended only for the individual or entity to which it is
addressed and contains information that is private and confidential. If
you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying is strictly prohibited. If you
have received this e-mail in error please delete it immediately and
advise us by return e-mail to hostmaster@foreshore.net


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users


Benjamin Boksa
b.boksa@sidebysite.de

side by site GmbH & Co. KG
Druckgestaltung & Webdesign

Barbarastr. 3-9 (Block 6)
D-50735 Koeln

Telefon: +49 221 2790964
Telefax: +49 221 2790965

http://www.sidebysite.de/


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

Hi Jesse,

Would it be possible to get that expires header built into the next
release of RT web UI? We did some limited customization of our UI, but
when we installed RT-2-0-6, we had to remove it all, re-install and then
re-customise to actually make the browser realize that there had been a
change (it didn’t even revert back to the default 2.0.6 pages, even
though the files had been replaced & restarting the server did nothing).

Thanks,

AndrewOn Friday, September 7, 2001, at 01:52 AM, Jesse Vincent wrote:

Derek:

Try inserting this line in WebRT/Elements/Header. If that
makes it better with IE5, I’ll drop this into 2.0.7.

-j

On Thu, Sep 06, 2001 at 05:09:08PM +0200, Benjamin Boksa wrote:

Hi Derek!

I had the same problem on several webpages I made when IE 5.5 came out.

I solved it in a very simple way: I just send an expiration date with
the
http-header which is some years in the past. You can do this with
mod_perl
or by putting:

in the HTML-code.

That should fix the problem with IE 5.5, as it forces the browser to
reload
the page every time the page is visited.

I hope this helped you solve your problem.

Regards,

Benjamin Boksa

Hi there,

We seem to have a problem where when we click on links we are getting
cached
versions of the pages, and have to hit F5 to refresh (IE 5.5).

Is there some sort of setting within RT (or Apache) we can set to
stop this
happening?

Regards,

Derek…




Any views expressed in this message are those of the individual
sender,
except where the sender states them to be the views of Foreshore
Limited.

This e-mail is intended only for the individual or entity to which it
is
addressed and contains information that is private and confidential.
If
you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying is strictly prohibited. If you
have received this e-mail in error please delete it immediately and
advise us by return e-mail to hostmaster@foreshore.net


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users


Benjamin Boksa
b.boksa@sidebysite.de

side by site GmbH & Co. KG
Druckgestaltung & Webdesign

Barbarastr. 3-9 (Block 6)
D-50735 Koeln

Telefon: +49 221 2790964
Telefax: +49 221 2790965

http://www.sidebysite.de/


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users


http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Andrew Yager
Real World Technology Solutions
Real People Real SolUtions™
ph: (02) 9945 2567 fax: (02) 9945 2566
mob: 0405 15 2568

Would it be possible to get that expires header built into the next

release of RT web UI? We did some limited customization of our UI, but

I’m not able to reproduce this problem on IE5.5, but other people have
repeatedly reported problems with this browser. My IE is configured to
"Check for new versions of a page on every visit to that page". Maybe
(hopefully) that solves everything for everybody?

You can find this option in Tools - Internet Options - Temporary
Internet Files - Settings.

Martin

Martin Schapendonk, martin@schapendonk.org, Phone: +31 (0)6 55770237
Student Information Systems and Management at Tilburg University

-----Original Message-----
From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com]On Behalf Of Martin Schapendonk
Sent: 07 September 2001 09:34
To: Andrew Yager
Cc: Jesse Vincent; rt-users@lists.fsck.com; Derek Fage; Benjamin Boksa
Subject: Re: [rt-users] v2.0.6 Browser caching problems

Would it be possible to get that expires header built into the next

release of RT web UI? We did some limited customization of our UI, but

I’m not able to reproduce this problem on IE5.5, but other people have
repeatedly reported problems with this browser. My IE is configured to
"Check for new versions of a page on every visit to that page". Maybe
(hopefully) that solves everything for everybody?

You can find this option in Tools - Internet Options - Temporary
Internet Files - Settings.

I wonder how much is ISP hidden caches also playing part, I know of 3 UK
ISP’s that have a hidden cache/proxy and its a nightmare as they don’t work
as they should!

Regards
Darren

Hi,

What I find strange is that it doesn’t update when I re-install, but if
I go in and physically change one of the files, it updates that file -
but only that file.
… I find this strange (and I think it must be something to do with
mod_perl or apache) - seeing as any of the other files (eg footer file),
still retain their pre-update form…

Let me try and be more specific… (just in case that makes no sense)

We have modified the header file to be more personalized to our company.
When we re-installed RT 2.0.6, all of our files were replaced (we backed
them up before hand). However, the update did not appear on the website.
When I went in, and updated the header file, the header file changed,
but none of the other files (eg footer) did.

If I went in and updated the footer file to include different content,
it got updated then.

AndrewOn Friday, September 7, 2001, at 06:36 PM, Darren Casey wrote:

-----Original Message-----
From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com]On Behalf Of Martin Schapendonk
Sent: 07 September 2001 09:34
To: Andrew Yager
Cc: Jesse Vincent; rt-users@lists.fsck.com; Derek Fage; Benjamin Boksa
Subject: Re: [rt-users] v2.0.6 Browser caching problems

On Fri, 7 Sep 2001, Andrew Yager wrote:

Would it be possible to get that expires header built into the next

release of RT web UI? We did some limited customization of our UI,

but

I’m not able to reproduce this problem on IE5.5, but other people have
repeatedly reported problems with this browser. My IE is configured to
"Check for new versions of a page on every visit to that page". Maybe
(hopefully) that solves everything for everybody?

You can find this option in Tools - Internet Options - Temporary
Internet Files - Settings.

I wonder how much is ISP hidden caches also playing part, I know of 3 UK
ISP’s that have a hidden cache/proxy and its a nightmare as they don’t
work
as they should!

Regards
Darren


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

Andrew Yager
Real World Technology Solutions
Real People Real SolUtions™
ph: (02) 9945 2567 fax: (02) 9945 2566
mob: 0405 15 2568

I suspect you’re running into the fact that mason’s cache uses the modtime
on templates to decide when to update its cached copies.

Also, you may want to stick your locally modified templates in local/WebRT/html, so they persist across upgrades. files in that directory structure
are automatically used by RT rather than their counterparts in the regular
directory structure.

-jOn Fri, Sep 07, 2001 at 07:18:15PM +1000, Andrew Yager wrote:

Hi,

What I find strange is that it doesn’t update when I re-install, but if
I go in and physically change one of the files, it updates that file -
but only that file.
… I find this strange (and I think it must be something to do with
mod_perl or apache) - seeing as any of the other files (eg footer file),
still retain their pre-update form…

Let me try and be more specific… (just in case that makes no sense)

We have modified the header file to be more personalized to our company.
When we re-installed RT 2.0.6, all of our files were replaced (we backed
them up before hand). However, the update did not appear on the website.
When I went in, and updated the header file, the header file changed,
but none of the other files (eg footer) did.

If I went in and updated the footer file to include different content,
it got updated then.

Andrew

On Friday, September 7, 2001, at 06:36 PM, Darren Casey wrote:

-----Original Message-----
From: rt-users-admin@lists.fsck.com
[mailto:rt-users-admin@lists.fsck.com]On Behalf Of Martin Schapendonk
Sent: 07 September 2001 09:34
To: Andrew Yager
Cc: Jesse Vincent; rt-users@lists.fsck.com; Derek Fage; Benjamin Boksa
Subject: Re: [rt-users] v2.0.6 Browser caching problems

On Fri, 7 Sep 2001, Andrew Yager wrote:

Would it be possible to get that expires header built into the next

release of RT web UI? We did some limited customization of our UI,

but

I’m not able to reproduce this problem on IE5.5, but other people have
repeatedly reported problems with this browser. My IE is configured to
"Check for new versions of a page on every visit to that page". Maybe
(hopefully) that solves everything for everybody?

You can find this option in Tools - Internet Options - Temporary
Internet Files - Settings.

I wonder how much is ISP hidden caches also playing part, I know of 3 UK
ISP’s that have a hidden cache/proxy and its a nightmare as they don’t
work
as they should!

Regards
Darren


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users


Andrew Yager
Real World Technology Solutions
Real People Real SolUtions™
ph: (02) 9945 2567 fax: (02) 9945 2566
mob: 0405 15 2568
http://www.rwts.com.au/



rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

The only thing I found worked was deleting all the WebRT files &
installing & modifying again.

AndrewOn Monday, September 10, 2001, at 01:34 AM, Adriaan Peeters wrote:

What I find strange is that it doesn’t update when I re-install, but
if
I go in and physically change one of the files, it updates that file -
but only that file.
… I find this strange (and I think it must be something to do with
mod_perl or apache) - seeing as any of the other files (eg footer
file),
still retain their pre-update form…

Let me try and be more specific… (just in case that makes no sense)

We have modified the header file to be more personalized to our
company.
When we re-installed RT 2.0.6, all of our files were replaced (we
backed
them up before hand). However, the update did not appear on the
website.
When I went in, and updated the header file, the header file changed,
but none of the other files (eg footer) did.

If I went in and updated the footer file to include different content,
it got updated then.

I suspect you’re running into the fact that mason’s cache uses the
modtime
on templates to decide when to update its cached copies.

And how can this be resolved ? I have the same problem, and I did stop
and
start apache, but I still get the old html code in my browser, it only
changes when I change a WebRT .html file.

In short: when I stop & start apache, the new RT2 files are not
loaded and
the previous version is still displayed. When I change a RT2 file,
that new
output is shown, but the other, not changed files still output as the
previous version.

Regards,
Adriaan Peeters

Andrew Yager
Real World Technology Solutions
Real People Real SolUtions™
ph: (02) 9945 2567 fax: (02) 9945 2566
mob: 0405 15 2568

In short: when I stop & start apache, the new RT2 files are not
loaded and
the previous version is still displayed. When I change a RT2 file,
that new
output is shown, but the other, not changed files still output as the
previous version.

The only thing I found worked was deleting all the WebRT files &
installing & modifying again.

Hmmz, there must be another way to resolve this !
I know I still get the old pages because when I try to reply or comment on a
ticket via the webinterface, I still get the [Non-text message not quoted]
message.

Any pointers on how to resolve this would be greatly appreciated ! (And yes,
I did restart apache :slight_smile:

Regards,
Adriaan Peeters

Sounds like your system clock is set funny such that mason isn’t picking up
the new components. blow away mason’s cache.On Mon, Sep 10, 2001 at 02:32:56AM +0200, Adriaan Peeters wrote:

In short: when I stop & start apache, the new RT2 files are not
loaded and
the previous version is still displayed. When I change a RT2 file,
that new
output is shown, but the other, not changed files still output as the
previous version.

The only thing I found worked was deleting all the WebRT files &
installing & modifying again.

Hmmz, there must be another way to resolve this !
I know I still get the old pages because when I try to reply or comment on a
ticket via the webinterface, I still get the [Non-text message not quoted]
message.

Any pointers on how to resolve this would be greatly appreciated ! (And yes,
I did restart apache :slight_smile:

Regards,
Adriaan Peeters

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

Sounds like your system clock is set funny such that mason isn’t picking
up
the new components. blow away mason’s cache.

How ? As I’m not perl or Mason wiz :frowning:

Thanks !
Adriaan Peeters

Sounds like your system clock is set funny such that mason isn’t picking
up
the new components. blow away mason’s cache.

How ? As I’m not perl or Mason wiz :frowning:

For the record: I did stop and start apache, but still the cached version is
used :frowning:

Hi Jesse,

I tried inserting the line as suggested, but am still seeing the same
problems.

Also tried somebody elses suggestion of modifying my internet settings to
always check for a newer page on every visit - still no joy.

After further investigation we are now faily sure that the problem is down
to our corporate proxy server, as if I modify the browser so that it does
not use the proxy server it all works fine.

The proxy server is Microsoft IAS (Internet Acceleration Server - Aaaarghhh)

Derek…From: Jesse Vincent [mailto:jesse@bestpractical.com]
Sent: 06 September 2001 16:53
To: Benjamin Boksa
Cc: Derek Fage; rt-users@lists.fsck.com
Subject: Re: [rt-users] v2.0.6 Browser caching problems

Derek:

Try inserting this line in WebRT/Elements/Header.  If that

makes it better with IE5, I’ll drop this into 2.0.7.

-j

Hi Derek!

I had the same problem on several webpages I made when IE 5.5 came out.

I solved it in a very simple way: I just send an expiration date with the
http-header which is some years in the past. You can do this with mod_perl
or by putting:

in the HTML-code.

That should fix the problem with IE 5.5, as it forces the browser to
reload
the page every time the page is visited.

I hope this helped you solve your problem.

Regards,

Benjamin Boksa

Hi there,

We seem to have a problem where when we click on links we are getting
cached

versions of the pages, and have to hit F5 to refresh (IE 5.5).

Is there some sort of setting within RT (or Apache) we can set to stop
this

happening?

Regards,

Derek…


Any views expressed in this message are those of the individual sender,
except where the sender states them to be the views of Foreshore
Limited.

This e-mail is intended only for the individual or entity to which it is
addressed and contains information that is private and confidential. If
you are not the intended recipient you are hereby notified that any
dissemination, distribution or copying is strictly prohibited. If you
have received this e-mail in error please delete it immediately and
advise us by return e-mail to hostmaster@foreshore.net


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users


Benjamin Boksa
b.boksa@sidebysite.de

side by site GmbH & Co. KG
Druckgestaltung & Webdesign

Barbarastr. 3-9 (Block 6)
D-50735 Koeln

Telefon: +49 221 2790964
Telefax: +49 221 2790965

http://www.sidebysite.de/


rt-users mailing list
rt-users@lists.fsck.com
http://lists.fsck.com/mailman/listinfo/rt-users

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

how about:

On Tue, Sep 11, 2001 at 11:15:42AM +0100, Derek Fage wrote: > Hi Jesse, > > I tried inserting the line as suggested, but am still seeing the same > problems. > > Also tried somebody elses suggestion of modifying my internet settings to > always check for a newer page on every visit - still no joy. > > After further investigation we are now faily sure that the problem is down > to our corporate proxy server, as if I modify the browser so that it does > not use the proxy server it all works fine. > > The proxy server is Microsoft IAS (Internet Acceleration Server - Aaaarghhh) > > Derek... > > -----Original Message----- > From: Jesse Vincent [mailto:jesse@bestpractical.com] > Sent: 06 September 2001 16:53 > To: Benjamin Boksa > Cc: Derek Fage; rt-users@lists.fsck.com > Subject: Re: [rt-users] v2.0.6 Browser caching problems > > > > Derek: > > Try inserting this line in WebRT/Elements/Header. If that > makes it better with IE5, I'll drop this into 2.0.7. > > > -j > > > > On Thu, Sep 06, 2001 at 05:09:08PM +0200, Benjamin Boksa wrote: > > Hi Derek! > > > > I had the same problem on several webpages I made when IE 5.5 came out. > > > > I solved it in a very simple way: I just send an expiration date with the > > http-header which is some years in the past. You can do this with mod_perl > > or by putting: > > > > > > > > in the HTML-code. > > > > That should fix the problem with IE 5.5, as it forces the browser to > reload > > the page every time the page is visited. > > > > I hope this helped you solve your problem. > > > > Regards, > > > > Benjamin Boksa > > > > > > > Hi there, > > > > > > We seem to have a problem where when we click on links we are getting > cached > > > versions of the pages, and have to hit F5 to refresh (IE 5.5). > > > > > > Is there some sort of setting within RT (or Apache) we can set to stop > this > > > happening? > > > > > > Regards, > > > > > > Derek... > > > > > > > > > > > > > **************************************************************************** > ** > > > ********* > > > Any views expressed in this message are those of the individual sender, > > > except where the sender states them to be the views of Foreshore > Limited. > > > > > > This e-mail is intended only for the individual or entity to which it is > > > addressed and contains information that is private and confidential. If > > > you are not the intended recipient you are hereby notified that any > > > dissemination, distribution or copying is strictly prohibited. If you > > > have received this e-mail in error please delete it immediately and > > > advise us by return e-mail to hostmaster@foreshore.net > > > > > > _______________________________________________ > > > rt-users mailing list > > > rt-users@lists.fsck.com > > > http://lists.fsck.com/mailman/listinfo/rt-users > > > > > > > > > > > -- > > Benjamin Boksa > > b.boksa@sidebysite.de > > > > side by site GmbH & Co. KG > > Druckgestaltung & Webdesign > > > > Barbarastr. 3-9 (Block 6) > > D-50735 Koeln > > > > Telefon: +49 221 2790964 > > Telefax: +49 221 2790965 > > > > http://www.sidebysite.de/ > > > > > > _______________________________________________ > > rt-users mailing list > > rt-users@lists.fsck.com > > http://lists.fsck.com/mailman/listinfo/rt-users > > > > -- > http://www.bestpractical.com/products/rt -- Trouble Ticketing. Free. > > _______________________________________________ > rt-users mailing list > rt-users@lists.fsck.com > http://lists.fsck.com/mailman/listinfo/rt-users >

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.

how about:

And for HTTP/1.1, I
believe.