- From: Rolf H. Nelson <rnelson@w3.org>
- Date: Thu, 15 Apr 1999 14:29:28 -0400
- To: onime@ictp.trieste.it
- CC: Dietmar_Schindler@mra.man.de, www4mail-comments@w3.org
I agree that the best thing to do is talk to the webmaster rather than
make up fictitious values for the referrer field. Making up false
values, such as the dirname, could confuse webmasters.
-Rolf
>>>>> "ONIME" == ONIME EHIMIKA OHIREIME <onime@ictp.trieste.it> writes:
> Well, Yes, I must say this is a possiblity that escaped me. the
> HTTP_REFERER. Well, I think that the immediate solution would
> be to talk to the web master of the site. For now we would list
> it as one of those categories of sites that www4mail cannot
> access.
> Thanks Clement Onime
> On Thu, 15 Apr 1999, Dietmar Schindler wrote:
>> >Date: Wed, 14 Apr 1999 11:39:39 +0200 (MET DST) >From: ONIME
>> EHIMIKA OHIREIME <onime@ictp.trieste.it>
>> >
>> >Normally just sending the URL
>> >http://bohl.minot.com/DFP.cgi?990331 to the www4mail >server
>> should do the trick. >But what I expect is that the site needs
>> to set some cookies that are >found on the homepage
>> http://bohl.minot.com
>>
>> Dear Clement Onime,
>>
>> I suspect that the site checks the HTTP Referer field. If this
>> was the case, the problem could actually be solved if www4mail
>> provided the possibility for the user to specify a Referer in
>> his request and would hand over the given Referer to the web
>> site in its HTTP request. A simplified cure could be that
>> www4mail always specified as Referer the dirname of the
>> requested URL.
>>
>> Saluton! Dietmar P. Schindler
>>
--
| Rolf Nelson (rolf@w3.org), Project Manager, W3C at MIT
| "Try to learn something about everything
| and everything about something." --Huxley
Received on Thursday, 15 April 1999 14:29:45 UTC