Re: [OT] Redirect w/ Netscape browser causing 'Document contains no data'

[Taisuke Yamada]

>> I seem to have a strange problem here with Netscape displaying the error
>> 'Document contains no data' when I do $Response->Redirect($location).
> 
> everytime i've ever gotten that it was because
> my server side code had caused an apache process to core dump.

You might want to try sending single byte ("\n" would be sufficient)
after calling above redirection code. Though it was not mod_perl (I
was using PHP), I had similar symptom and it went away after I added
this extra code.

Hope this helps.

--
Taisuke Yamada <[EMAIL PROTECTED]>
PGP fingerprint = 6B 57 1B ED 65 4C 7D AE  57 1B 49 A7 F7 C8 23 46

Re: [OT] Redirect w/ Netscape browser causing 'Document contains no data'

[Joel W. Reed]

On Aug 23, [EMAIL PROTECTED] contorted a few electrons to say...
Daniel Little wrote:
> 
> I seem to have a strange problem here with Netscape displaying the error
> 'Document contains no data' when I do $Response->Redirect($location).
> 

everytime i've ever gotten that it was because my
server side code had caused an apache process to core dump.

jr

-- 

Joel W. Reed412-257-3881
--All the simple programs have been written.



 PGP signature

Re: [OT] Redirect w/ Netscape browser causing 'Document contains no data'

[Joshua Chamas]

Daniel Little wrote:
> 
> I seem to have a strange problem here with Netscape displaying the error
> 'Document contains no data' when I do $Response->Redirect($location).
> 
> I'm using Apache 1.3.19, mod_perl 1.25, Apache::ASP v2.09, but I don't think
> it's in Apache::ASP, as the redirect code in there looks pretty much the
> same as what is recommended in the guide. We have a front-end proxy
> configuration that also has mod_proxy_add_forward installed, but that was
> only added recently and I've been trying to track this problem down for a
> little while.
> 
> Looking at the logs, both the frontend and backend servers are logging a
> status code of '302', with '0' bytes transferred - just like I would expect
> it to. If I go directly to the backend server, it makes no difference,
> either. It also doesn't seem to make any difference if I buffer output or
> not. All of this, of course, works just fine in IE.
> 

Maybe the URL being redirected to is getting mangled by
ProxyPassReverse.  I would see what headers are coming out
of your web page, my favorite for this is lwp-request ...

  lwp-request -ed http://yoursite/yourpage.asp

Maybe you can see the Location: header output and go from there?

--Josh

_
Joshua Chamas   Chamas Enterprises Inc.
NodeWorks Founder   Huntington Beach, CA  USA 
http://www.nodeworks.com1-714-625-4051