Webware for Python

All
I've just installed apache and webware app server with success but am
wondering if anyon ehas this working with Resin?


thanks

Eric

Dear our Guests=2C

EXPLORE TURKEY WITH ASTARTETOURS!!
=09
Hotel Reservations=3A 
You will find more than 200 hotels all over Turkey=2C which have been carefully selected=2E
Through our reservation system we are able to book more than 1=2E000 hotels arround Europe=2E
 
Tours 
Hosted Programs=2C sightseeing tours=2C escorted tours or cruise programs=2E
We have tours on set dates each year or we can organize special itineraries for the independant traveller or small groups!!
 

Rent-A-Car=3A
Travelling on your own pace in Turkey! We have a range of vehicles on offer to choose from=2E They may be hired in all major cities=2E 
Your car can be made available at the airport or your hotel for collection!!

Visit our web-site!!

www=2Eastartetours=2Ecom

Kind Regards
Astarte Tours

P=2ES=2E=3A If you want to unsubscribe=2C please sent us an e-mail=2E

Ian Bicking wrote:
> If you read the HTTP spec, there's a particular response code that is
> best to use in this situation, but I can't remember which it is (it's in
> the 300's).

Interesting...

(from http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3)

10.3.4 303 See Other
The response to the request can be found under a different URI and 
SHOULD be retrieved using a GET method on that resource. This method 
exists primarily to allow the output of a POST-activated script to 
redirect the user agent to a selected resource. The new URI is not a 
substitute reference for the originally requested resource. The 303 
response MUST NOT be cached, but the response to the second (redirected) 
request might be cacheable.

The different URI SHOULD be given by the Location field in the response. 
Unless the request method was HEAD, the entity of the response SHOULD 
contain a short hypertext note with a hyperlink to the new URI(s).

       Note: Many pre-HTTP/1.1 user agents do not understand the 303
       status. When interoperability with such clients is a concern, the
       302 status code may be used instead, since most user agents react
       to a 302 response as described here for 303.