Thanks!! Actually, it's a java based app on the WebSphere app server that
sends the response to Apache web server which in turn sends the response to
the browser. I tested the reports directly on the App server which are
working fine. I suspect something is wrong in the apache config. I also
checke
On Tue, Nov 3, 2009 at 2:26 PM, Marcin 'Rambo' Roguski
wrote:
> On Tue, 3 Nov 2009 14:20:27 -0500
> b k wrote:
>
>> Hi all,
>> PDF reports are not being generated on any browser. [...]Any help would be
>> greatly
>> appreciated
>
> Send Content-Type: application/pdf or application/octet-stre
Begin forwarded message:
From: Lars Eilebrecht
Date: November 3, 2009 5:12:20 PM PST
To: committ...@apache.org
Subject: Free Live Video Streaming of ApacheCon US 2009 Keynotes,
and Hadoop, HTTPD and Lucene Sessions
If you can't make it to Oakland, don't miss the FREE live video
streams.
On Tue, 3 Nov 2009 14:20:27 -0500
b k wrote:
> Hi all,
> PDF reports are not being generated on any browser. [...]Any help would be
> greatly
> appreciated
Send Content-Type: application/pdf or application/octet-stream from your PDF
generator
text/html is just plain wrong.
--
Maslow's Ma
Hi all,
PDF reports are not being generated on any browser. On IE, I get the File
Save dialog and on Firefox, all weird characters get displayed. When I ran
this test again with HTTPFox and Fiddler, I noticed that the content-type in
the response header is *text/html* for this PDF report, which is
b k wrote:
Thanks!! Actually, it's a java based app on the WebSphere app server that
sends the response to Apache web server which in turn sends the response to
the browser. I tested the reports directly on the App server which are
working fine. I suspect something is wrong in the apache config.
On Tue, Nov 3, 2009 at 3:06 PM, b k wrote:
> Thanks!! Actually, it's a java based app on the WebSphere app server that
> sends the response to Apache web server which in turn sends the response to
> the browser. I tested the reports directly on the App server which are
> working fine. I suspect so
Raj Iyer wrote:
I am currently dealing with a situation where the Apache httpd process
becomes unresponsive for some time. At the end of this time, the Apache
error log shows:
[Mon Nov 2 13:27:49 2009] [warn] child process 7310 did not exit,
sending another SIGHUP
[Mon Nov 2 13:27:49 2009] [w
Marcos Mendez wrote:
Hi,
Is there an easy way to configure mod_proxy to let certain ports
passthru? I've got a couple of rewrite rules on port 80, but don't
know how to do that for SSL/443 for example so that the proxy does not
get involved.
For a simple answer, without digging into what you a
Hi,
Is there an easy way to configure mod_proxy to let certain ports
passthru? I've got a couple of rewrite rules on port 80, but don't
know how to do that for SSL/443 for example so that the proxy does not
get involved.
Regards,
Marcos
--
On Tue, 2009-11-03 at 17:03 +, Raj Iyer wrote:
> [Mon Nov 2 13:27:49 2009] [warn] child process 751 did not exit,
> sending another SIGHUP
Child process not responding to singals indicates a very very serious
system-level issue.
$ uname -a ?
Try ktrace/strace the child PID as well
~BAS
-
Hello,
I am currently dealing with a situation where the Apache httpd process
becomes unresponsive for some time. At the end of this time, the Apache
error log shows:
[Mon Nov 2 13:27:49 2009] [warn] child process 7310 did not exit,
sending another SIGHUP
[Mon Nov 2 13:27:49 2009] [warn]
I was incorrect in my statement that the HTTP filter was not being added, error
in my log statement. It actually is being added and the change affecting my
application is here. Hopefully someone might be able explain why the change
was made and perhaps offer a suggestion as to what I would nee
Hello All,
This is the continuation of a thread that was titled "Increase Logging" but
that doesn't seem to make much sense anymore so I am starting a new thread.
The core of the problem is that my application sends a POST message which goes
through the mod_isapi module to a MSFT ISAPI dll. W
Hi,
When I try the access using "http://localhost:23456"; I get a web page display "It
works".
Is there a way of telling the browser or apache to use this port by default?
It depends on linux-distribution but there is usually a file named
"ports.conf" where you can set the default port. Se
> When I try the access using "http://localhost:23456"; I get a web page display
> "It works".
> Is there a way of telling the browser or apache to use this port by default?
When you connect using a URL like http:/www.example.com or
http://localhost, your browser will use port 80 to connect as th
16 matches
Mail list logo
