'Rendering Develop'

Hello. I'm fairly new to Lightroom and I am currently using version 2.7 on a mac. I have been using it for about 6 months now and I have got the hang of most things, however, recently I noticed something that is becoming a problem for me.
I shoot in RAW and I am aware that once the pictures are imported into lightroom they are rendered and adjustments need to be made. My current workflow is as follows:
Import>organise pics>export image to photoshop>edit>save>make further adjustments in lightroom develop
It is at this point when I occasionally run into the problem I have been experiencing and I can not find anything on the net about this.
After I have finished editing a picture in develop, that is either quite warm or cold looking (through my own choice), I go back to the library to organise my albums. At this point the message 'rendering develop' appears. After a few seconds of the edited image being displayed, lightroom automatically changes the white balance. I do not want this to happen. I have the white balance set to 'As Shot'. I have also tried changing it to 'custom'. I have tried using the temperature arrows in Library mode to try and counteract the change. Library reverts to the edited image briefly and then goes back to what it decides the white balance should be. When exporting my edited pics, it is exported as the automatic change and not the one I actually want.
I can understand why lightroom changes the image properties on import but I do not know why it insists on doing it after the image has been edited. It only does it when the image looks warm or cold but this is the effect I want not how lightroom insists it should be. Is there a way I can turn this automatic feature off? It is really annoying me as I am unable to export my edited pics properly.
Kind regards.

OK I have done this. I renamed the file and Lightroom has created a new one. It seems to have stopped the previews from changing, for now. When exporting Lightroom is still changing the white balance, making my pics look lifeless. The only work around I can find is by exporting the image with the 'Lightroom Adjustments' back in to photoshop, re-correcting the white balance there and then saving it to a different location ready for uploading or printing.
If I have to do this everytime to get the white balance I want, it is going to make my editing much longer, not to mention creating duplicate files and possibly losing detail/quality? Surely there must be an easier way.

Similar Messages

Lightroom crashes when rendering Develop preview under Vista 64-bit

I'm running Windows Vista Ultimate 64-bit and Lightroom 1.1 crashes every time I click the "Develop" pane. My images are DNG files without the original RAW embedded.
Lightroom ONLY crashes when I load an image in Develop. If I open Develop without any image selected, it's fine (no image is displayed). I can zoom in to 100% in Library and it works fine. Exporting images to JPG works fine. Editing photos in the Library pane is fine. The crash data is:
Problem signature:
Problem Event Name: APPCRASH
Application Name: lightroom.exe
Application Version: 1.1.0.0
Application Timestamp: 4677e8e1
Fault Module Name: MFC80U.DLL
Fault Module Version: 8.0.50727.163
Fault Module Timestamp: 4484afec
Exception Code: c0000005
Exception Offset: 0002511c
OS Version: 6.0.6000.2.0.0.256.1
Locale ID: 1033
I've uninstalled LR 1.1 and reinstalled and it does the same thing. When I uninstall LR 1.1 and the install LR 1.0 (the previous version) Develop does open, but it doesn't render the images correctly - it looks like it misinterprets the white balance by about 1,500k degrees (very ugly), but Library shows the correct image/white-balance.
I've updated my nVidia 7900 graphics drivers to the latest version, appropriate to my OS and architecture. I've disabled XMP creation and Adobe Photo Downloader, as well as all other running applications (Antivirus, spyware, itunes, etc).
This USED to work fine in Vista and I did not make any significant changes, but I expect it's an issue with WindowsUpdate causing an incompatibility. I can't roll-back to my Vista state when it worked a month ago (that's another Vista frustration).
Anyway advice or comments would be GREATLY appreciated since this is an integral part of my professional workflow. I own a legitimate, licensed copy of both Lightroom and Vista, yet neither company is willing to talk to me unless I pay them money, which I think is complete extortion, but I digress.
Thanks in advance for your help.

Has anyone got a resolution on this? I have the same issue. Lightroom crashes when I click develop and the develop module begins to render the image. Clicking develop with no image selected allows the develop module to load however selecting develop on the menu bar and choosing either previous photo or next photo causes lightroom to crash while rendering an image.
I have a 64 bit capable HP XW8400 workstation with 2 dual core Xeon processors, 4 GB RAM, and a nVidia FX 4400 graphics card. This video card was put in as a test. the original video card was an nVidia quadra NVS something. When I ran the NVS card I used the drivers certified for Adobe CS2. I am running 32 bit Windows XP SP2 with all current updates. I do not have any MS office components installed on this system.
I read of some troubles around the Realtek HD audio driver and some Adobe applications (not Lightroom). Since I have this sound device I disabled it and removed the drivers...still crashes.
I also disabled the Intel VT in the system bios (I believe this is required to run 64 bit XP or Vista)... no change. Also disabled the NX feature...no change.
I also loaded VMware workstation 6.0 and installed Lightroom in a 32bit Windows XP SP2 VM. In the VM Lightroom works perfectly on the same machine...just not as snappy...
This stinks...Lightroom works perfectly on my poky laptop.

Rendering: Larger Preview.... Stalls in Library Module.

I am running Lightroom 2.4 on a Windows Vista system. I have found recently that when I use the library module and attempt to zoom in on a picture in that module the full size picture on screen reverts to a highly pixalated view (presumably the embeded low res jpeg from the Nikon RAW file) and I get the message "Rendering: Larger Preview..." and nothing at all happens. If I then select the develop module the picture renders correctly, if following this I select the library module again all used to be well but now I get the message "Rendering:Develop..." and again nothing happening.
Has anyone encountered this problem and discovered a solution?

John
Thanks for the input. The problem certainly happens then but I am getting
it other times as well. I found some advice on the forum about the problem
which suggests it is associated with MS Vista's complex file access
permision system. It appears you have to give all users read write and
execute permission on all your Lightroom files. I am trying that to see if
it solves the problem.
Thanks again
Dave

Loading Aperture images into Pages doc

Have Aperture 2.1.4 and Pages '09. When using the Media tool to load images from the Aperture library (w/ images stored on internal HD), only option given is to load iPhoto images; Aperture does not appear and I do not use iPhoto. When I have tried to navigate to an onboard Aperture Library using Edit>Choose, my Aperture libraries are unable to be selected. What is the best solution?

Henrik Holmegaard wrote:
Hmm ... interesting idea. If the idea is to drag and drop unrendered ('undeveloped') raw image data into page, why does the system not permit this without indicating an intervening application to render ('develop') the raw image data? Somewhere, somehow there has to be rendering ('developing') of raw image data of which there are as many formats as there are makes and models of digital camera, so it might make sense for the system to ask for software that is able to do the rendering ('developing').
Maybe in a future version but, at this time, Pages clearly states:
Pages accepts all QuickTime-supported formats, including the following graphics file types:
• TIFF
• GIF
• JPEG
• PDF
• PSD
• EPS
• PICT
I'm not sure that this statement let us guess that Aperture files are accepted.
If someone want to insert such a file, why not build an Automator process grabbing the file,
developping it
then inserting it in Pages ?
Apple delivers tools but can't use them for us !
Yvan KOENIG (VALLAURIS, France) mardi 6 octobre 2009 11:00:52

As a JSF Developer, I want to understand technically how the JSF View Components are rendered as html and how there events are binded to Server.I want to know each Java Class that is involved in flow.

As a JSF Developer, I want to understand technically how the JSF View Components are rendered as html and how there events are binded to Server.I want to know how flows goes to the server and server understands the method which is to be called of managed bean. I know it is with annotation @ManagedBean and method name, but how Call is binded with annotation @ManagedBean.
In short, i want to know the internal implementation of JSF Framework.

As a JSF Developer, I want to understand technically how the JSF View Components are rendered as html and how there events are binded to Server.I want to know how flows goes to the server and server understands the method which is to be called of managed bean. I know it is with annotation @ManagedBean and method name, but how Call is binded with annotation @ManagedBean.
In short, i want to know the internal implementation of JSF Framework.

Rendering issue in Develop Module

Slow rendering has been discussed in many threads, but can anyone explain what is going on with this specific issue I am having?
If I am working in the Develop Module and I render two raw files at 1:1, after the initial rendering delay I can generally toggle between the two and they are rendered almost instantaneously. I assume this is because some info has been stored in the ACR Cache and Lightroom can quickly display them. Now if I render a 3rd raw file at 1:1 and try to toggle between 3 images, one of them always needs 10 seconds or so to load/render. What is happening here? I thought the purpose of the ACR Cache was to allow for fast rendering of previously rendered images. I currently have my ACR Cache set to 10GB and I have recently purged it, so I am nowhere near the limit. Other system/software specs as follows:
LR 5.2
NEF files from Nikon D7100 (approx 30MB)
iMac 27-inch 2560x1440
OS 10.8.5
Processor: 3.06 GHz Intel Core 2 Duo
RAM: 16GB
Video Card: ATI Radeon HD 4670 (256MB)
Storage: 1TB SATA 7200rpm, 25% full

LanceBenedict wrote:
Thanks for the explanation on the RAM caching. If I am understanding you correctly on the ACR Cache, it sounds like it is essentially useless once you have applied some editing to the image because you need to wait on those edits to be rendered.
No, I wouldn't agree that it's useless. When you load an image into Develop you'll be presented first with a brief view of your Library preview, which should quickly be replaced with the ACR Cache "scene-referred" preview that will have any existsing edits applied before you see it. That should all happen quite quickly, and when that preview is loaded the sliders will be activated. When that happens you can start work, even though the full file is being rendered in background, and there is no need to wait until the "Loading" indicator goes out (as I said earlier, you can turn that off if you prefer).
So the benefit of the ACR Cache entry is that it allows you to start work in Develop whilst the original file is still being fully converted.
Note that although we are talking specifically about the ACR Cache entry, the same holds true for DNG Fast Load Data and/or Smart Previews. Which one of those 3 is initially used depends on what exists at the time of loading, and what file type is being used. But the same principle applies to all three.
In terms of reducing the rendering time, that's a more problematical issue as there are various factors in the pipeline which come into play, any one (or more) of which may be sub-optimal. These factors include:
1. Size of the files being loaded. It should go without saying that 36mp files from a Nikon 800 are going to take quite a bit longer that the 10mp files from say a Canon 40D.
2. Location of the files and speed of the interface, i.e. expect image files on a USB2 connected hard drive spinning at 5400rpm to be a lot slower to load than if they were on a 7200rpm drive internally connected on a 6gb/s Sata hub.
3. Once the data has been read, how fast is the CPU.....rendering a raw file will be quite a CPU-intensive task, so the faster the processor the better.
4. User expectation.....one man's "painfully slow" could be another's "quite acceptable".
With that in mind, I have no idea if what you are experiencing is "typical" or too slow. Putting it into context, all my original files are on a fast internal drive on a 3gb/s connection, I have an i7-930 quad-core processor (now over 3 years old, so not leading edge by any means), 12gb of RAM. Full loading times in Develop are now about 3 seconds per image when using 22mp files from a Canon 5D3.
Looking at the things you've tried, purging the ACR Cache and increasing its size would have no effect unless:
a) There was a problem with the existing cache, and
b) You regenerated new cache entries
Discarding old previews and rebuilding would have had no effect on Develop loading times, nor would downsizing the dimensions of the develop window.
Increasing system RAM should certainly be beneficial to other areas of Lightroom, I'm just not sure it would have a specific benefit to image loading into Develop. That might be dependant upon what else was running in the system at the time.

Loupe and Grid view rendering not as good as Develop view.

I recently see that while using LR 5.6 the images rendered in the loupe and grid views do not look nearly as good as the same image displayed in the develop view. I have screen grabs if you'd like to see them below. The Loupe and grid are not as saturated and the gradient in the sky is not nearly as smooth. If I bounce between 'E' and 'D' it is pretty obvious. Once in a while the 'E' (loupe) view looks the same. I'm afraid that I will delete an image based on what I see in the Loupe or do unnecessary edits on an image. When I exported to jpg, the images looked pretty good.
Grid:
Loupe:
Develop:

As far as what could be contributing to a difference, other than an actual bug:
LR Previews are stored as AdobeRGB JPGs, so Library previews go from LR-Internal color profile to AdobeRGB to Display color profile, whereas Develop previews go directly from LR-Internal color profile to Display color profile. If there are some colors that are outside of AdobeRGB then some conversion may occur. The conversion to 8-bit JPG is also probably adding banding that Develop wouldn’t show. There might also be Relative vs Perceptual color profile conversion differences occurring. I don’t know the specifics of which is used for the Adobe color profile conversion and whether what you’re seeing is outside the expected variations.
If you view at less than 1:1/100% zoom, especially with Fit or Fill, then small details that vary across the group of original image pixels that are displayed as one display pixel can be averaged differently due to differences in the downsampling algorithms used between computing Library file previews and computing Develop display previews where Develop’s is built for speed because it occurs in real-time after every slider movement, where Library previews are computed in the background and so can use a more accurate resampling algorithm. Usually this is only a difference in sharp/smoothness but it can also manifest as a difference in tone if there are lots of tiny noise spots getting averaged together inaccurately in Develop or more accurately in Library.
Since I can see only a tiny difference between Library and Develop on my monitor in this particular example, I can't imagine that small difference is enough to reject the Library version and accept the Develop version. Maybe you're seeing others with more differences?

Updated to LR 5.4, images now importing extremely slow. After importing and rendering images are still very slow to go through and develop. No issues in LR 5.3 which was very fast.

After importing and rendering images are still very slow to go through and develop. No issues in LR 5.3 which was very fast. Canon,Nikon, Leica and Fuji files all rendering slow. iMac 2.9 ghz 16gb RAM OSX 10.8.5. Catalogs and images are kept on external drives. Drives running fine. Really need a fix on this since I'm norally imported and processing at least 4,000 images per LR Catalog. Is there way to revert back to 5.3? I can't use 5.4 is its current state. Thanks.

Download LR 5.3 and install it
By the way, lots of people have this complaint about LR 5.4, and the advice I give is to use LR 5.3 unless you need one of the new camera models supported by LR 5.4

Possible to preview Safari 7 rendered ajax content in developer toolbar?

So in Chrome, Firefox (via Firebug), etc there is the ability to preview the rendered response of an ajax request. So if the response comes back in HTML, the developer toolbar has the option of viewing it rendered. This is super helpful when dealing with something like Symfony framework where 500 errors trigger a HTML error page. When using Safari, I have to scan the ajax response's HTML for the error whereas in other browsers, it shows me the rendered content so I can just read the error.
Is there a way to get Safari to render the returned ajax content rather than or in addition to just showing its source?
Thanks!
Alan

You might do better to ask in the Developers forum here. Sounds more liek teh type of things discussed there:
Developer Forums

Please develop rendering support for traditional mongolian script.

A major barrier for me to move from Window to Mac is that Mac doesn't have rendering support for my own language: traditional Mongolian, whereas Microsoft does it pretty well. For example, for this major news website in traditional Mongolian: http://www.mgyxw.net/, IE is able to show everything but Mac cannot. Please develop this support as soon as possible (and also the keyboard input support as Microsoft did).

Acidophiniz wrote:
Microsoft does it pretty well. For example, for this major news website in traditional Mongolian: http://www.mgyxw.net/,
Could you post a screen shot? It looks to me like the text of this site is not in standard unicode, but in some sort of private use area encoding. If that is the case, you can be sure Apple will never support display of this page. Have you installed some special custom font to see it?
A correct Unicode page is at
http://babelstone.co.uk/Test/Mongolian.html

Developer 11g not rendering buttons proper size

Forms Developer 11.1.2.1.0 on Linux with X-ming to a Windows 7 workstation.
In the canvas editor, buttons render as lines in a blue box. The box is the correct size, but the button doesn't fill the space. You can't read the button label and therefore can't size it properly.
How do I get the buttons to render correctly?
Thanks.
I would provide an image, but that is disabled.

Hi,
but isn't the valid hint name buttons ?
http://docs.oracle.com/cd/E16162_01/apirefs.1112/e17491/tagdoc/af_navigationPane.html
Frank

Webpage rendering is very slow on max (os10.4.x; firefox 3.6.10) This is a recent development. Rendering on Vista PC is very fast. Why?

In the past 3 days website rendering on my mac is very slow (25 sec to render NYTimes page). This happens on 2 macs (os 10.4.x; firefox 3.6.10) and second mac is (os 10.5.x and firefox 3.6.10). Started recently. Most webpages take 15 to 25 seconds to render. Onsame network a pc laptop renders in 3 sec. What might the problem be?

fixed with this method:
http://bbs.archlinux.org/viewtopic.php?pid=319710

PHP refuses to be rendered

Hi,
I've used the default PHP installation on OSX with no problems in the past (after uncommenting the 2 lines in httpd and enabling Personal Web Sharing), but after a recent reinstallation of the operating system (having re-updated all software) PHP refuses to render. HTML files render fine, but when I load up a PHP file, its source is displayed instead of being properly rendered. I like to think I know what I'm doing, but I'm befuddled :/
Any help would be much appreciated.
Here's my httpd.conf, if it helps:
<pre>
## httpd.conf -- Apache HTTP server configuration file
# Based upon the NCSA server configuration files originally by Rob McCool.
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:<a class="jive-link-external-small" href="http://">http://httpd.apache.org/docs/> for detailed information about
# the directives.
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
# After this file is processed, the server will look for and process
# /private/etc/httpd/srm.conf and then /private/etc/httpd/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do not begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
### Section 1: Global Environment
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
ServerType standalone
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:<a class="jive-link-external-small" href="http://">http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
ServerRoot "/usr"
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USEFCNTL_SERIALIZEDACCEPT or
# USEFLOCK_SERIALIZEDACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename.
#LockFile "/private/var/run/httpd.lock"
# PidFile: The file in which the server should record its process
# identification number when it starts.
PidFile "/private/var/run/httpd.pid"
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this. But if yours does (you'll know because
# this file will be created when you run Apache) then you must ensure that
# no two invocations of Apache share the same scoreboard file.
ScoreBoardFile "/private/var/run/httpd.scoreboard"
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order. The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults. You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#ResourceConfig /private/etc/httpd/srm.conf
#AccessConfig /private/etc/httpd/access.conf
# Timeout: The number of seconds before receives and sends time out.
Timeout 300
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
KeepAlive On
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
MaxKeepAliveRequests 100
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
KeepAliveTimeout 15
# Server-pool size regulation. Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
# It does this by periodically checking how many servers are waiting
# for a request. If there are fewer than MinSpareServers, it creates
# a new spare. If there are more than MaxSpareServers, some of the
# spares die off. The default values are probably OK for most sites.
MinSpareServers 5
MaxSpareServers 10
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
StartServers 5
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
MaxClients 150
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
MaxRequestsPerChild 0
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
#Listen 3000
#Listen 12.34.56.78:80
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#BindAddress *
# Dynamic Shared Object (DSO) Support
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available before they are used.
# Please read the file http://httpd.apache.org/docs/dso.html for more
# details about the DSO mechanism and run `httpd -l' for the list of already
# built-in (statically linked and thus always available) modules in your httpd
# binary.
# Note: The order in which modules are loaded is important. Don't change
# the order below without expert advice.
# Example:
# LoadModule foo_module libexec/mod_foo.so
#LoadModule vhostaliasmodule libexec/httpd/modvhostalias.so
#LoadModule env_module libexec/httpd/mod_env.so
LoadModule configlogmodule libexec/httpd/modlogconfig.so
#LoadModule mimemagicmodule libexec/httpd/modmimemagic.so
LoadModule mime_module libexec/httpd/mod_mime.so
LoadModule negotiation_module libexec/httpd/mod_negotiation.so
#LoadModule status_module libexec/httpd/mod_status.so
#LoadModule info_module libexec/httpd/mod_info.so
LoadModule includes_module libexec/httpd/mod_include.so
LoadModule autoindex_module libexec/httpd/mod_autoindex.so
LoadModule dir_module libexec/httpd/mod_dir.so
LoadModule cgi_module libexec/httpd/mod_cgi.so
LoadModule asis_module libexec/httpd/mod_asis.so
LoadModule imap_module libexec/httpd/mod_imap.so
LoadModule action_module libexec/httpd/mod_actions.so
#LoadModule speling_module libexec/httpd/mod_speling.so
LoadModule userdir_module libexec/httpd/mod_userdir.so
LoadModule alias_module libexec/httpd/mod_alias.so
LoadModule rewrite_module libexec/httpd/mod_rewrite.so
LoadModule access_module libexec/httpd/mod_access.so
LoadModule auth_module libexec/httpd/mod_auth.so
#LoadModule anonauthmodule libexec/httpd/modauthanon.so
#LoadModule dbmauthmodule libexec/httpd/modauthdbm.so
#LoadModule digest_module libexec/httpd/mod_digest.so
#LoadModule proxy_module libexec/httpd/libproxy.so
#LoadModule cernmetamodule libexec/httpd/modcernmeta.so
#LoadModule expires_module libexec/httpd/mod_expires.so
#LoadModule headers_module libexec/httpd/mod_headers.so
#LoadModule usertrack_module libexec/httpd/mod_usertrack.so
LoadModule logforensicmodule libexec/httpd/modlogforensic.so
#LoadModule uniqueidmodule libexec/httpd/moduniqueid.so
LoadModule setenvif_module libexec/httpd/mod_setenvif.so
#LoadModule dav_module libexec/httpd/libdav.so
#LoadModule ssl_module libexec/httpd/libssl.so
#LoadModule perl_module libexec/httpd/libperl.so
LoadModule php4_module libexec/httpd/libphp4.so
LoadModule hfsapplemodule libexec/httpd/modhfsapple.so
# Reconstruction of the complete module list from all available modules
# (static and shared ones) to achieve correct module execution order.
# [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE UPDATE THIS, TOO]
ClearModuleList
#AddModule modvhostalias.c
#AddModule mod_env.c
AddModule modlogconfig.c
#AddModule modmimemagic.c
AddModule mod_mime.c
AddModule mod_negotiation.c
#AddModule mod_status.c
#AddModule mod_info.c
AddModule mod_include.c
AddModule mod_autoindex.c
AddModule mod_dir.c
AddModule mod_cgi.c
AddModule mod_asis.c
AddModule mod_imap.c
AddModule mod_actions.c
#AddModule mod_speling.c
AddModule mod_userdir.c
AddModule mod_alias.c
AddModule mod_rewrite.c
AddModule mod_access.c
AddModule mod_auth.c
#AddModule modauthanon.c
#AddModule modauthdbm.c
#AddModule mod_digest.c
#AddModule mod_proxy.c
#AddModule modcernmeta.c
#AddModule mod_expires.c
#AddModule mod_headers.c
#AddModule mod_usertrack.c
AddModule modlogforensic.c
#AddModule moduniqueid.c
AddModule mod_so.c
AddModule mod_setenvif.c
#AddModule mod_dav.c
#AddModule mod_ssl.c
#AddModule mod_perl.c
AddModule mod_php4.c
AddModule modhfsapple.c
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#ExtendedStatus On
### Section 2: 'Main' server configuration
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
# If your ServerType directive (set earlier in the 'Global Environment'
# section) is set to "inetd", the next few directives don't have any
# effect since their settings are defined by the inetd configuration.
# Skip ahead to the ServerAdmin directive.
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
Port 80
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
# User/Group: The name (or #number) of the user/group to run httpd as.
# . On SCO (ODT 3) use "User nouser" and "Group nogroup".
# . On HPUX you may not be able to use shared memory as nobody, and the
# suggested workaround is to create a user www and use that user.
# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# when the value of (unsigned)Group is above 60000;
# don't use Group "#-1" on these systems!
User nobody
Group nobody
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents.
ServerAdmin [email protected]
# ServerName allows you to set a host name which is sent back to clients for
# your server if it's different than the one the program would get (i.e., use
# "www" instead of the host's real name).
# Note: You cannot just invent host names and hope they work. The name you
# define here must be a valid DNS name for your host. If you don't understand
# this, ask your network administrator.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#ServerName new.host.name
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
DocumentRoot "/Users/borischerny/Sites"
# Each directory to which Apache has access, can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
# First, we configure the "default" to be a very restrictive set of
# permissions.
<Directory />
Options FollowSymLinks
AllowOverride None
</Directory>
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
# This should be changed to whatever you set DocumentRoot to.
<Directory "/Users/borischerny/Sites">
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
# Note that "MultiViews" must be named explicitly --- "Options All"
# doesn't give it to you.
Options Indexes FollowSymLinks MultiViews
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
AllowOverride None
# Controls who can get stuff from this server.
Order allow,deny
Allow from all
</Directory>
# UserDir: The name of the directory which is appended onto a user's home
# directory if a ~user request is received.
<IfModule mod_userdir.c>
UserDir public_html
</IfModule>
# Control access to UserDir directories. The following is an example
# for a site where these directories are restricted to read-only.
#<Directory /home/*/public_html>
# AllowOverride FileInfo AuthConfig Limit
# Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec
# <Limit GET POST OPTIONS PROPFIND>
# Order allow,deny
# Allow from all
# </Limit>
# <LimitExcept GET POST OPTIONS PROPFIND>
# Order deny,allow
# Deny from all
# </LimitExcept>
#</Directory>
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index. Separate multiple entries with spaces.
<IfModule mod_dir.c>
DirectoryIndex index.html
</IfModule>
# AccessFileName: The name of the file to look for in each directory
# for access control information.
AccessFileName .htaccess
# The following lines prevent .htaccess files from being viewed by
# Web clients. Since .htaccess files often contain authorization
# information, access is disallowed for security reasons. Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files. If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
<Files ~ "^\.([Hh][Tt]|[Dd][Ss]_[Ss])">
Order allow,deny
Deny from all
Satisfy All
</Files>
# Apple specific filesystem protection.
<Files "rsrc">
Order allow,deny
Deny from all
Satisfy All
</Files>
<Directory ~ ".*\.\.namedfork">
Order allow,deny
Deny from all
Satisfy All
</Directory>
# CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each
# document that was negotiated on the basis of content. This asks proxy
# servers not to cache the document. Uncommenting the following line disables
# this behavior, and proxies will be allowed to cache the documents.
#CacheNegotiatedDocs
# UseCanonicalName: (new for 1.3) With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name. With this setting off, Apache will
# use the hostname:port that the client supplied, when possible. This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
UseCanonicalName On
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
<IfModule mod_mime.c>
TypesConfig /private/etc/httpd/mime.types
</IfModule>
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
DefaultType text/plain
# The modmimemagic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
# modmimemagic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include modmimemagic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
<IfModule modmimemagic.c>
MIMEMagicFile /private/etc/httpd/magic
</IfModule>
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
HostnameLookups Off
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you do define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
ErrorLog "/private/var/log/httpd/error_log"
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
LogLevel warn
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you do
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and not in this file.
CustomLog "/private/var/log/httpd/access_log" common
# If you would like to have agent and referer logfiles, uncomment the
# following directives.
#CustomLog "/private/var/log/httpd/referer_log" referer
#CustomLog "/private/var/log/httpd/agent_log" agent
# If you prefer a single logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog "/private/var/log/httpd/access_log" combined
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
ServerSignature On
# EBCDIC configuration:
# (only for mainframes using the EBCDIC codeset, currently one of:
# Fujitsu-Siemens' BS2000/OSD, IBM's OS/390 and IBM's TPF)!!
# The following default configuration assumes that "text files"
# are stored in EBCDIC (so that you can operate on them using the
# normal POSIX tools like grep and sort) while "binary files" are
# stored with identical octets as on an ASCII machine.
# The directives are evaluated in configuration file order, with
# the EBCDICConvert directives applied before EBCDICConvertByType.
# If you want to have ASCII HTML documents and EBCDIC HTML documents
# at the same time, you can use the file extension to force
# conversion off for the ASCII documents:
# > AddType text/html .ahtml
# > EBCDICConvert Off=InOut .ahtml
# EBCDICConvertByType On=InOut text/* message/* multipart/*
# EBCDICConvertByType On=In application/x-www-form-urlencoded
# EBCDICConvertByType On=InOut application/postscript model/vrml
# EBCDICConvertByType Off=InOut /
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
<IfModule mod_alias.c>
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
Alias /icons/ "/usr/share/httpd/icons/"
<Directory "/usr/share/httpd/icons">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
# This Alias will project the on-line documentation tree under /manual/
# even if you change the DocumentRoot. Comment it if you don't want to
# provide access to the on-line documentation.
Alias /manual/ "/Library/WebServer/Documents/manual/"
<Directory "/Library/WebServer/Documents/manual">
Options Indexes FollowSymlinks MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
ScriptAlias /cgi-bin/ "/Library/WebServer/CGI-Executables/"
# "/Library/WebServer/CGI-Executables" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/Library/WebServer/CGI-Executables">
AllowOverride None
Options None
Order allow,deny
Allow from all
</Directory>
</IfModule>
# End of aliases.
# Redirect allows you to tell clients about documents which used to exist in
# your server's namespace, but do not anymore. This allows you to tell the
# clients where to look for the relocated document.
# Format: Redirect old-URI new-URL
# Directives controlling the display of server-generated directory listings.
<IfModule mod_autoindex.c>
# FancyIndexing is whether you want fancy directory indexing or standard
IndexOptions FancyIndexing
# AddIcon* directives tell the server which icon to show for different
# files or filename extensions. These are only displayed for
# FancyIndexed directories.
AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip
AddIconByType (TXT,/icons/text.gif) text/*
AddIconByType (IMG,/icons/image2.gif) image/*
AddIconByType (SND,/icons/sound2.gif) audio/*
AddIconByType (VID,/icons/movie.gif) video/*
AddIcon /icons/binary.gif .bin .exe
AddIcon /icons/binhex.gif .hqx
AddIcon /icons/tar.gif .tar
AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv
AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip
AddIcon /icons/a.gif .ps .ai .eps
AddIcon /icons/layout.gif .html .shtml .htm .pdf
AddIcon /icons/text.gif .txt
AddIcon /icons/c.gif .c
AddIcon /icons/p.gif .pl .py
AddIcon /icons/f.gif .for
AddIcon /icons/dvi.gif .dvi
AddIcon /icons/uuencoded.gif .uu
AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl
AddIcon /icons/tex.gif .tex
AddIcon /icons/bomb.gif core
AddIcon /icons/back.gif ..
AddIcon /icons/hand.right.gif README
AddIcon /icons/folder.gif ^^DIRECTORY^^
AddIcon /icons/blank.gif ^^BLANKICON^^
# DefaultIcon is which icon to show for files which do not have an icon
# explicitly set.
DefaultIcon /icons/unknown.gif
# AddDescription allows you to place a short description after a file in
# server-generated indexes. These are only displayed for FancyIndexed
# directories.
# Format: AddDescription "description" filename
#AddDescription "GZIP compressed document" .gz
#AddDescription "tar archive" .tar
#AddDescription "GZIP compressed tar archive" .tgz
# ReadmeName is the name of the README file the server will look for by
# default, and append to directory listings.
# HeaderName is the name of a file which should be prepended to
# directory indexes.
ReadmeName README.html
HeaderName HEADER.html
# IndexIgnore is a set of filenames which directory indexing should ignore
# and not include in the listing. Shell-style wildcarding is permitted.
IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t
</IfModule>
# End of indexing directives.
# Document types.
<IfModule mod_mime.c>
# AddLanguage allows you to specify the language of a document. You can
# then use content negotiation to give a browser a file in a language
# it can understand.
# Note 1: The suffix does not have to be the same as the language
# keyword --- those with documents in Polish (whose net-standard
# language code is pl) may wish to use "AddLanguage pl .po" to
# avoid the ambiguity with the common suffix for perl scripts.
# Note 2: The example entries below illustrate that in quite
# some cases the two character 'Language' abbreviation is not
# identical to the two character 'Country' code for its country,
# E.g. 'Danmark/dk' versus 'Danish/da'.
# Note 3: In the case of 'ltz' we violate the RFC by using a three char
# specifier. But there is 'work in progress' to fix this and get
# the reference data for rfc1766 cleaned up.
# Danish (da) - Dutch (nl) - English (en) - Estonian (ee)
# French (fr) - German (de) - Greek-Modern (el)
# Italian (it) - Korean (kr) - Norwegian (no) - Norwegian Nynorsk (nn)
# Portugese (pt) - Luxembourgeois* (ltz)
# Spanish (es) - Swedish (sv) - Catalan (ca) - Czech(cs)
# Polish (pl) - Brazilian Portuguese (pt-br) - Japanese (ja)
# Russian (ru)
AddLanguage da .dk
AddLanguage nl .nl
AddLanguage en .en
AddLanguage et .ee
AddLanguage fr .fr
AddLanguage de .de
AddLanguage el .el
AddLanguage he .he
AddCharset ISO-8859-8 .iso8859-8
AddLanguage it .it
AddLanguage ja .ja
AddCharset ISO-2022-JP .jis
AddLanguage kr .kr
AddCharset ISO-2022-KR .iso-kr
AddLanguage nn .nn
AddLanguage no .no
AddLanguage pl .po
AddCharset ISO-8859-2 .iso-pl
AddLanguage pt .pt
AddLanguage pt-br .pt-br
AddLanguage ltz .lu
AddLanguage ca .ca
AddLanguage es .es
AddLanguage sv .sv
AddLanguage cs .cz .cs
AddLanguage ru .ru
AddLanguage zh-TW .zh-tw
AddCharset Big5 .Big5 .big5
AddCharset WINDOWS-1251 .cp-1251
AddCharset CP866 .cp866
AddCharset ISO-8859-5 .iso-ru
AddCharset KOI8-R .koi8-r
AddCharset UCS-2 .ucs2
AddCharset UCS-4 .ucs4
AddCharset UTF-8 .utf8
# LanguagePriority allows you to give precedence to some languages
# in case of a tie during content negotiation.
# Just list the languages in decreasing order of preference. We have
# more or less alphabetized them here. You probably want to change this.
<IfModule mod_negotiation.c>
LanguagePriority en da nl et fr de el it ja kr no pl pt pt-br ru ltz ca es sv tw
</IfModule>
# AddType allows you to tweak mime.types without actually editing it, or to
# make certain files to be certain types.
AddType application/x-tar .tgz
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
# Despite the name similarity, the following Add* directives have nothing
# to do with the FancyIndexing customization directives above.
AddEncoding x-compress .Z
AddEncoding x-gzip .gz .tgz
# If the AddEncoding directives above are commented-out, then you
# probably should define those extensions to indicate media types:
#AddType application/x-compress .Z
#AddType application/x-gzip .gz .tgz
# AddHandler allows you to map certain file extensions to "handlers",
# actions unrelated to filetype. These can be either built into the server
# or added with the Action command (see below)
# If you want to use server side includes, or CGI outside
# ScriptAliased directories, uncomment the following lines.
# To use CGI scripts:
#AddHandler cgi-script .cgi
# To use server-parsed HTML files
#AddType text/html .shtml
#AddHandler server-parsed .shtml
# Uncomment the following line to enable Apache's send-asis HTTP file
# feature
#AddHandler send-as-is asis
# If you wish to use server-parsed imagemap files, use
#AddHandler imap-file map
# To enable type maps, you might want to use
#AddHandler type-map var
</IfModule>
# End of document types.
# Action lets you define media types that will execute a script whenever
# a matching file is called. This eliminates the need for repeated URL
# pathnames for oft-used CGI file processors.
# Format: Action media/type /cgi-script/location
# Format: Action handler-name /cgi-script/location
# MetaDir: specifies the name of the directory in which Apache can find
# meta information files. These files contain additional HTTP headers
# to include when sending the document
#MetaDir .web
# MetaSuffix: specifies the file name suffix for the file containing the
# meta information.
#MetaSuffix .meta
# Customizable error response (Apache style)
# these come in three flavors
# 1) plain text
#ErrorDocument 500 "The server made a boo boo.
# n.b. the single leading (") marks it as text, it does not get output
# 2) local redirects
#ErrorDocument 404 /missing.html
# to redirect to local URL /missing.html
#ErrorDocument 404 /cgi-bin/missing_handler.pl
# N.B.: You can redirect to a script or a document using server-side-includes.
# 3) external redirects
#ErrorDocument 402 http://some.other-server.com/subscription_info.html
# N.B.: Many of the environment variables associated with the original
# request will not be available to such a script.
# Customize behaviour based on the browser
<IfModule mod_setenvif.c>
# The following directives modify normal HTTP response behavior.
# The first directive disables keepalive for Netscape 2.x and browsers that
# spoof it. There are known problems with these browser implementations.
# The second directive is for Microsoft Internet Explorer 4.0b2
# which has a broken HTTP/1.1 implementation and does not properly
# support keepalive when it is used on 301 or 302 (redirect) responses.
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0
# The following directive disables HTTP/1.1 responses to browsers which
# are in violation of the HTTP/1.0 spec by not being able to grok a
# basic 1.1 response.
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0
</IfModule>
# End of browser customization directives
# Allow server status reports, with the URL of http://servername/server-status
# Change the ".your-domain.com" to match your domain to enable.
#<Location /server-status>
# SetHandler server-status
# Order deny,allow
# Deny from all
# Allow from .your-domain.com
#</Location>
# Allow remote server configuration reports, with the URL of
# http://servername/server-info (requires that mod_info.c be loaded).
# Change the ".your-domain.com" to match your domain to enable.
#<Location /server-info>
# SetHandler server-info
# Order deny,allow
# Deny from all
# Allow from .your-domain.com
#</Location>
# There have been reports of people trying to abuse an old bug from pre-1.1
# days. This bug involved a CGI script distributed as a part of Apache.
# By uncommenting these lines you can redirect these attacks to a logging
# script on phf.apache.org. Or, you can record them yourself, using the script
# support/phfabuselog.cgi.
#<Location /cgi-bin/phf*>
# Deny from all
# ErrorDocument 403 http://phf.apache.org/phfabuselog.cgi
#</Location>
# Proxy Server directives. Uncomment the following lines to
# enable the proxy server:
#<IfModule mod_proxy.c>
# ProxyRequests On
# <Directory proxy:*>
# Order deny,allow
# Deny from all
# Allow from .your-domain.com
# </Directory>
# Enable/disable the handling of HTTP/1.1 "Via:" headers.
# ("Full" adds the server version; "Block" removes all outgoing Via: headers)
# Set to one of: Off | On | Full | Block
# ProxyVia On
# To enable the cache as well, edit and uncomment the following lines:
# (no cacheing without CacheRoot)
# CacheRoot "/private/var/run/proxy"
# CacheSize 5
# CacheGcInterval 4
# CacheMaxExpire 24
# CacheLastModifiedFactor 0.1
# CacheDefaultExpire 1
# NoCache a-domain.com another-domain.edu joes.garage-sale.com
#</IfModule>
# End of proxy directives.
### Section 3: Virtual Hosts
# VirtualHost: If you want to maintain multiple domains/hostnames on your
# machine you can setup VirtualHost containers for them. Most configurations
# use only name-based virtual hosts so the server doesn't need to worry about
# IP addresses. This is indicated by the asterisks in the directives below.
# Please see the documentation at <URL:<a class="jive-link-external-small" href="http://">http://www.apache.org/docs/vhosts/>
# for further details before you try to setup virtual hosts.
# You may use the command line option '-S' to verify your virtual host
# configuration.
# Use name-based virtual hosting.
#NameVirtualHost *:80
# VirtualHost example:
# Almost any Apache directive may go into a VirtualHost container.
# The first VirtualHost section is used for requests without a known
# server name.
#<VirtualHost *:80>
# ServerAdmin [email protected]
# DocumentRoot /www/docs/dummy-host.example.com
# ServerName dummy-host.example.com
# ErrorLog logs/dummy-host.example.com-error_log
# CustomLog logs/dummy-host.example.com-access_log common
#</VirtualHost>
</pre>

sorry i forgot that... i use php5 so i guessed at the module name... upon looking closer at the conf its mod_php4.c
<pre>
<IfModule mod_php4.c>
AddType application/x-httpd-php .php
</IfModule>
</pre>

Windows developed report hangs on Unix Reports server ??

Hi,
We recently migrated from a Windows BI tier to HP-UX Itanium. The problem I have is that one particular report just hangs in the Unix reports server. The basics of the report are that it has repeating frames which displays three record blocks per page. I use a formatting trigger on a derived field to alternate the background colour of the frames.
After making several modifications to the report I've discovered that the trigger to alternate the background colour is the issue. I can use the same field with a trigger to say conditionally display a field or hide another frame and that works ok. I can set the background of the frame to another colour and the report works fine.
As soon as I use a formatting trigger to change the background it hangs.
In terms of report development I'm stuck with only Windows as Report builder is not available for our platform so troubleshooting this is a tedious process.
Has anyone seen anything like this before ????
Cheers,
Ron

hello,
oracle reports has always had this dependency. it needs the x environemtn for rendering of the output. so you need an active xsession for the reports server to point DISPLAY to.
a possible work around is the use of a soft-terminal such as VNC or xvfb (see oracle9i application server release notes for details).
regards,
philipp

Kindly help to develop alv grid display

Hi ,
I have a requirement in which I need to display ALV GRID display and in its tool bar 4 butons are required. In the same view down to alv display i want to develop a tabstrip and its functionalities.I have designed classic alv using SALV_WD_TABLE component. I want a good GRID Display, not like flat field names that comes in list display, looking for bulged fields(like what comes for ALV GRID in normal abap) display with print version etc hidden and buttons at the top of ALV. Kindly help
Highly rewarded
Kindly help
Regards,
Lakshmi
Edited by: Lakshmi Menon on Nov 27, 2008 4:49 PM

Well Web Dynpro is generally output in HTML so the output formatting is never going to quite look like a desktop application (which is the case with the ALV Grid). You have very little control over the look of the column headers. In fact you can only manipulate what is available via the Portal Theme.
There is a new Tradeshow Plus theme available in NetWeaver 7.01 which uses a gradiant background for the column headers. This gives them a little more depth:
http://www.flickr.com/photos/tjung/3068850120/
The other option is next year when NetWeaver Business Client version 3.0 comes out, you will be able to render Web Dynpro applications using the NWBC Smart Client Rendering. This will render Web Dynpro applications using desktop libraries instead of HTML/Browser. This gives Web Dynpro a more SAPGUI/Desktop appears of course.
http://www.flickr.com/photos/tjung/2685619882/in/set-72157606418550143/

'Rendering Develop'

Similar Messages

Maybe you are looking for