Problem with loadMovie with IE over https connection

Hi,
Using Flash 8, Apache 2.2. I have my Apache server set to
require a client certificate. If I call loadMovie() and attempt to
retrieve an image that's stored on my server, IE will not display
the image. However, Firefox will display the image with no problem.
I've narrowed the problem down to the client certificate
requirement - if I don't require a client certificate, IE will
display the image, but as soon as I require a client certificate,
the image will no longer display. And as I stated earlier, the
image will successfully appear in Firefox with or without the
requirement to have a valid client certificate.
Any ideas?
Thanks,
Stan McFarland

Is the content being loaded from the same domain as the
application? I know we had a problem when the Flex App was trying
to call a different server that enforces Client Authentication from
one that doesn't. FF recognizes that and pops up the "select a
cert" dialog, but IE doesn't -- you just get the "Stream Error" or
whatever. Make sure you're authenticated first, then try loading
the asset...
- Kevin

Similar Messages

Class not found error over HTTPS connection

Problem: Facing problem in downloading signed JAR file over HTTPS connection.
While downloading the jar file over a https connection, i get a certificate with following message
" Do you want to accept the certificate from web site <server name> for the purpose of exchanging encrypted information? "
If i accept the ceritificate immediately without any delay, all goes fine. The jar file gets downloaded and the applet runs withoput any problem. But if we accept the certificate after some delay say after one or two minutes i get "Class not found error"
Has anybody come across any such issue ?
Thanks in advance.
Rohit

I got the same error. I believe the ssl connection has a short timeout.
But I don't think this is a bug because there is no sense in letting a ssl connection open in the initial state before accepting the server's certificate.

The dialogs doesn't show up over HTTPS connection.

JWS usually shows Version check and Launching dialog when it start up.
But when it started over HTTPS connection, those dialogs doesn't show up.
When we use HTTP connection, the application launch by following step.
1. Java loading dialog shows
2. Version check dialog shows
3. Launching application dialog shows
4. Application launched
However, in the case of HTTPS connection, step2, 3's dialog doesn't show up.
(It might be skipped? What's going on?)
I think that the step1,2,3 are processed by JavaWebStart.
Is there any way to show these dialogs when we use HTTPS connection?
Client: Windows XP(SP2), JDK: 1.4.2_06
Web Server: WebLogic(ver.8.1)

When running over http or file protocol, these dialogs are shown if the update check takes more than 1500 ms, when application must be updated before launching (due in 1.5.0 to offline-allowed not being specified, or setting <update check="always" /> in 6.0) (assuming target isn't using basic authentication). If the update check can complete in less time than that, then the dialogs will not be shown.
For https, there is a probability that the attempted https connection will cause https security dialogs, which would then always cause the check to take more than 1500 seconds (or whatever timeout is configured) so webstart won't show the download progress dialog untill it knows there is an update.
This should be a bug, since it is handled beter in BasicAuthentication case.
If you are using Authentication, the download dialog will show up only after 1500 ms if the JAuthenticator chalange dialog is not being shown.
Similarilly, using https, he dialog should show after 1500 ms (or whatever timeout) if the https security dialog, or host mismatch dialog is not showmin.
/Andy

Connecting with database using setproperty over SOAP connection

The following method connects to a MySQL database.
public void setDBDriverName(String in)
     dbDriverName = in;
public void setDBConnection(String in)
     dbConnection = in;
public void connectToMySQLDatabase() throws SQLException
     if(dbCon == null)
             try
                Class.forName(dbDriverName);     // SQL driver
                dbCon = DriverManager.getConnection(dbConnection);           // JDBC url
                s = dbCon.createStatement();
                   catch (Exception e)
                System.out.println("Could not connect to database using " + dbConnection + " at " + dbDriverName + " : " + e.getMessage());
     else
          System.out.println("Could not connect to databse : Already connected");
}The method is part of a webservice, in which I use setproperties to set the database connection because the webservice must work with different types of databases like Oracle and MySQL.
<jsp:useBean id="ContactHistorieClassid" scope="request" class="proxy.soap.ContactHistorieClassProxy" />
     <jsp:setProperty name="ContactHistorieClassid" property="DBConnection" value="org.gjt.mm.mysql.Driver" />
     <jsp:setProperty name="ContactHistorieClassid" property="DBDriverName" value="jdbc:mysql://localhost/contacthistorie" />
     <jsp:setProperty name="ContactHistorieClassid" property="clientID" value="1" />
<%
     ContactHistorieClassid.connectToMySQLDatabase();
%>What am I doing wrong here?

Forgot what happens, sorry. After trying to use the ContactHistorieClassid.connectToMySQLDatabase() method, my server console tells me that it cannot connect to the database, even though it returns the values as they were set in the setproperty.
When I manually enter the values like this...
Class.forName("org.gjt.mm.mysql.Driver");     // SQL driver
dbCon = DriverManager.getConnection("jdbc:mysql://localhost/contacthistorie"); .. it works properly. So the setproperties are executed as the should be.

Unable to play movie over HTTPS

I have this flash movie which was created using Captivate,
now the problem is it wont play over HTTPS connection- only the
playback control show up and all i get is blank screen. The actual
tutorial never starts, but as soon as i change it to HTTP it works
great. I am new to captivate and really need to fix this, Can
anyone please help me or point me to a solutions to this. Would be
much appreciated. Thanks!!!

Hi there tech_varun
I'm thinking this is something you should report to Adobe as
a potential bug. To do that, you use the Wish Form.
Click
here to view the WishForm/Bug Reporting Form
Since things work under normal HTTP but fail under HTTPS. I
looked the code over and really don't see anything that would seem
to inhibit a HTTPS connection. So I'm wondering if it's got
something to do with the _skin.swf actually calling the main part
of the movie. I suppose we might confirm that to some extent by
asking you to publish with Borders turned off. (Project > Skin
> Borders tab and DE-select "Show Borders")
Copy that output to the HTTPS server and see if the project
seems to run.
Cheers... Rick

HTTPS connections timeout with Security Update 2010-001

I recently installed Security Update 2010-001 onto Snow Leopard and have difficulty accessing certain web sites from my browser (I have tried with both Safari and Firefox and they have the same problem). The issue in common with the problem sites is that they use akamai mirror servers to deliver their content over HTTPS connections. I can see from the Activity window that the redirected HTTPS connections to the akamai sites just hang and eventually timeout. This is new behaviour since installing the security patch and I was wondering if the Open SLL update in the security patch may have caused these connections to hang? Anyone have any idea (or where I could find out?)
P

I recently installed Security Update 2010-001 onto Snow Leopard and have difficulty accessing certain web sites from my browser (I have tried with both Safari and Firefox and they have the same problem). The issue in common with the problem sites is that they use akamai mirror servers to deliver their content over HTTPS connections. I can see from the Activity window that the redirected HTTPS connections to the akamai sites just hang and eventually timeout. This is new behaviour since installing the security patch and I was wondering if the Open SLL update in the security patch may have caused these connections to hang? Anyone have any idea (or where I could find out?)
P

Http connection to ABAP problem

Hey Gurus,
I have a problem with the configuration of a http connection to an ABAP system (type H ). Due to the PI Development Book I shall set up a connection called "XI_Integrationserver".
The target host is: saptest8 , port 50000.
The path prefix is: /sap/xi/engine/?type=entry
client
user: PIAPPLUSER
When I test the connection I get an 404 (Not found) error. But it should be an 500 (internal server error). In transaction SICF the engine is started. I don't know how to solve this problem. Please help me!
I'm using PI 7.01!!!
Thanks for any reply.

Hi,
the name does not matter, but "XI_Integrationserver" is missleading because the target is an application system, better would be "INTEGR_ENG_SAPTEST8"
Assumedly the port is wrong. Did you put the port of the ABAP WAS? Transaction SMICM / GoTo / Services
Regards,
Udo

[solved] Owncloud over SSL: http works, but over https only apache

Hello,
I try to setup owncloud with SSL.
Accessing over http works, but over https, I reach the default apache page instead of the owncloud page.
(I set up SSL according to https://wiki.archlinux.org/index.php/LAMP#SSL )
How could I make the owncloud site available over https?
relevant files:
owncloud.conf:
<IfModule mod_alias.c>
Alias /owncloud /usr/share/webapps/owncloud/
</IfModule>
<Directory /usr/share/webapps/owncloud/>
Options FollowSymlinks
Require all granted
php_admin_value open_basedir "/srv/http/:/home/:/tmp/:/usr/share/pear/:/usr/share/webapps/owncloud/:/etc/webapps/owncloud/:/mt/daten/owncloud/"
</Directory>
<VirtualHost *:80>
ServerAdmin [email protected]
DocumentRoot /usr/share/webapps/owncloud
ServerName http://example.com/owncloud
</VirtualHost>
I tried to change 80 to 443, but then, systemctl restart httpd didn't work. (apache failed)
httpd.conf:
# This is the main Apache HTTP server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.
# In particular, see
# <URL:http://httpd.apache.org/docs/2.4/mod/directives.html>
# for a discussion of each configuration directive.
# 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.
# 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/access_log"
# with ServerRoot set to "/usr/local/apache2" will be interpreted by the
# server as "/usr/local/apache2/logs/access_log", whereas "/logs/access_log"
# will be interpreted as '/logs/access_log'.
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
# Do not add a slash at the end of the directory path. If you point
# ServerRoot at a non-local disk, be sure to specify a local disk on the
# Mutex directive, if file-based mutexes are used. If you wish to share the
# same ServerRoot for multiple httpd daemons, you will need to change at
# least PidFile.
ServerRoot "/etc/httpd"
# Mutex: Allows you to set the mutex mechanism and mutex file directory
# for individual mutexes, or change the global defaults
# Uncomment and change the directory if mutexes are file-based and the default
# mutex file directory is not on a local disk or is not appropriate for some
# other reason.
# Mutex default:/run/httpd
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, instead of the default. See also the <VirtualHost>
# directive.
# Change this to Listen on specific IP addresses as shown below to
# prevent Apache from glomming onto all bound IP addresses.
#Listen 12.34.56.78:80
Listen 80
<IfModule mod_ssl.c>
Listen 443
</IfModule>
# 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.
# Statically compiled modules (those listed by `httpd -l') do not need
# to be loaded here.
# Example:
# LoadModule foo_module modules/mod_foo.so
LoadModule authn_file_module modules/mod_authn_file.so
#LoadModule authn_dbm_module modules/mod_authn_dbm.so
#LoadModule authn_anon_module modules/mod_authn_anon.so
#LoadModule authn_dbd_module modules/mod_authn_dbd.so
#LoadModule authn_socache_module modules/mod_authn_socache.so
LoadModule authn_core_module modules/mod_authn_core.so
LoadModule authz_host_module modules/mod_authz_host.so
LoadModule authz_groupfile_module modules/mod_authz_groupfile.so
LoadModule authz_user_module modules/mod_authz_user.so
#LoadModule authz_dbm_module modules/mod_authz_dbm.so
#LoadModule authz_owner_module modules/mod_authz_owner.so
#LoadModule authz_dbd_module modules/mod_authz_dbd.so
LoadModule authz_core_module modules/mod_authz_core.so
#LoadModule authnz_ldap_module modules/mod_authnz_ldap.so
LoadModule access_compat_module modules/mod_access_compat.so
LoadModule auth_basic_module modules/mod_auth_basic.so
#LoadModule auth_form_module modules/mod_auth_form.so
#LoadModule auth_digest_module modules/mod_auth_digest.so
#LoadModule allowmethods_module modules/mod_allowmethods.so
#LoadModule file_cache_module modules/mod_file_cache.so
#LoadModule cache_module modules/mod_cache.so
#LoadModule cache_disk_module modules/mod_cache_disk.so
#LoadModule cache_socache_module modules/mod_cache_socache.so
LoadModule socache_shmcb_module modules/mod_socache_shmcb.so
#LoadModule socache_dbm_module modules/mod_socache_dbm.so
#LoadModule socache_memcache_module modules/mod_socache_memcache.so
#LoadModule watchdog_module modules/mod_watchdog.so
#LoadModule macro_module modules/mod_macro.so
#LoadModule dbd_module modules/mod_dbd.so
#LoadModule dumpio_module modules/mod_dumpio.so
#LoadModule echo_module modules/mod_echo.so
#LoadModule buffer_module modules/mod_buffer.so
#LoadModule data_module modules/mod_data.so
#LoadModule ratelimit_module modules/mod_ratelimit.so
LoadModule reqtimeout_module modules/mod_reqtimeout.so
#LoadModule ext_filter_module modules/mod_ext_filter.so
#LoadModule request_module modules/mod_request.so
LoadModule include_module modules/mod_include.so
LoadModule filter_module modules/mod_filter.so
#LoadModule reflector_module modules/mod_reflector.so
#LoadModule substitute_module modules/mod_substitute.so
#LoadModule sed_module modules/mod_sed.so
#LoadModule charset_lite_module modules/mod_charset_lite.so
#LoadModule deflate_module modules/mod_deflate.so
#LoadModule xml2enc_module modules/mod_xml2enc.so
#LoadModule proxy_html_module modules/mod_proxy_html.so
LoadModule mime_module modules/mod_mime.so
#LoadModule ldap_module modules/mod_ldap.so
LoadModule log_config_module modules/mod_log_config.so
#LoadModule log_debug_module modules/mod_log_debug.so
#LoadModule log_forensic_module modules/mod_log_forensic.so
#LoadModule logio_module modules/mod_logio.so
#LoadModule lua_module modules/mod_lua.so
LoadModule env_module modules/mod_env.so
#LoadModule mime_magic_module modules/mod_mime_magic.so
#LoadModule cern_meta_module modules/mod_cern_meta.so
#LoadModule expires_module modules/mod_expires.so
LoadModule headers_module modules/mod_headers.so
#LoadModule ident_module modules/mod_ident.so
#LoadModule usertrack_module modules/mod_usertrack.so
#LoadModule unique_id_module modules/mod_unique_id.so
LoadModule setenvif_module modules/mod_setenvif.so
LoadModule version_module modules/mod_version.so
#LoadModule remoteip_module modules/mod_remoteip.so
LoadModule proxy_module modules/mod_proxy.so
LoadModule proxy_connect_module modules/mod_proxy_connect.so
LoadModule proxy_ftp_module modules/mod_proxy_ftp.so
LoadModule proxy_http_module modules/mod_proxy_http.so
LoadModule proxy_fcgi_module modules/mod_proxy_fcgi.so
LoadModule proxy_scgi_module modules/mod_proxy_scgi.so
#LoadModule proxy_fdpass_module modules/mod_proxy_fdpass.so
LoadModule proxy_wstunnel_module modules/mod_proxy_wstunnel.so
LoadModule proxy_ajp_module modules/mod_proxy_ajp.so
LoadModule proxy_balancer_module modules/mod_proxy_balancer.so
LoadModule proxy_express_module modules/mod_proxy_express.so
#LoadModule session_module modules/mod_session.so
#LoadModule session_cookie_module modules/mod_session_cookie.so
#LoadModule session_crypto_module modules/mod_session_crypto.so
#LoadModule session_dbd_module modules/mod_session_dbd.so
LoadModule slotmem_shm_module modules/mod_slotmem_shm.so
#LoadModule slotmem_plain_module modules/mod_slotmem_plain.so
LoadModule ssl_module modules/mod_ssl.so
#LoadModule dialup_module modules/mod_dialup.so
LoadModule lbmethod_byrequests_module modules/mod_lbmethod_byrequests.so
LoadModule lbmethod_bytraffic_module modules/mod_lbmethod_bytraffic.so
LoadModule lbmethod_bybusyness_module modules/mod_lbmethod_bybusyness.so
LoadModule lbmethod_heartbeat_module modules/mod_lbmethod_heartbeat.so
#LoadModule mpm_event_module modules/mod_mpm_event.so
LoadModule mpm_prefork_module modules/mod_mpm_prefork.so
LoadModule unixd_module modules/mod_unixd.so
#LoadModule heartbeat_module modules/mod_heartbeat.so
#LoadModule heartmonitor_module modules/mod_heartmonitor.so
#LoadModule dav_module modules/mod_dav.so
LoadModule status_module modules/mod_status.so
LoadModule autoindex_module modules/mod_autoindex.so
#LoadModule asis_module modules/mod_asis.so
#LoadModule info_module modules/mod_info.so
#LoadModule suexec_module modules/mod_suexec.so
#LoadModule cgid_module modules/mod_cgid.so
#LoadModule cgi_module modules/mod_cgi.so
#LoadModule dav_fs_module modules/mod_dav_fs.so
#LoadModule dav_lock_module modules/mod_dav_lock.so
#LoadModule vhost_alias_module modules/mod_vhost_alias.so
LoadModule negotiation_module modules/mod_negotiation.so
LoadModule dir_module modules/mod_dir.so
#LoadModule imagemap_module modules/mod_imagemap.so
#LoadModule actions_module modules/mod_actions.so
#LoadModule speling_module modules/mod_speling.so
LoadModule userdir_module modules/mod_userdir.so
LoadModule alias_module modules/mod_alias.so
#LoadModule rewrite_module modules/mod_rewrite.so
#own additions:
LoadModule php5_module modules/libphp5.so
<IfModule unixd_module>
# 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.
# It is usually good practice to create a dedicated user and group for
# running httpd, as with most system services.
User http
Group http
</IfModule>
# '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.
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents. e.g. [email protected]
ServerAdmin [email protected]
# ServerName gives the name and port that the server uses to identify itself.
# This can often be determined automatically, but we recommend you specify
# it explicitly to prevent problems during startup.
# If your host doesn't have a registered DNS name, enter its IP address here.
#ServerName www.example.com:80
# Deny access to the entirety of your server's filesystem. You must
# explicitly permit access to web content directories in other
# <Directory> blocks below.
<Directory />
Options FollowSymLinks
AllowOverride none
Require all denied
</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.
# 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 "/srv/http"
<Directory "/srv/http">
# Possible values for the Options directive are "None", "All",
# or any combination of:
# Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
# The Options directive is both complicated and important. Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
Options Indexes FollowSymLinks
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
# AllowOverride FileInfo AuthConfig Limit
AllowOverride None
# Controls who can get stuff from this server.
Require all granted
</Directory>
# DirectoryIndex: sets the file that Apache will serve if a directory
# is requested.
<IfModule dir_module>
DirectoryIndex index.html
</IfModule>
# The following lines prevent .htaccess and .htpasswd files from being
# viewed by Web clients.
<Files ".ht*">
Require all denied
</Files>
# 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 "/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
<IfModule log_config_module>
# 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
<IfModule logio_module>
# You need to enable mod_logio.c to use %I and %O
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio
</IfModule>
# 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 "/var/log/httpd/access_log" common
# If you prefer a logfile with access, agent, and referer information
# (Combined Logfile Format) you can use the following directive.
#CustomLog "/var/log/httpd/access_log" combined
</IfModule>
<IfModule alias_module>
# Redirect: Allows you to tell clients about documents that used to
# exist in your server's namespace, but do not anymore. The client
# will make a new request for the document at its new location.
# Example:
# Redirect permanent /foo http://www.example.com/bar
# Alias: Maps web paths into filesystem paths and is used to
# access content that does not live under the DocumentRoot.
# Example:
# Alias /webpath /full/filesystem/path
# If you include a trailing / on /webpath then the server will
# require it to be present in the URL. You will also likely
# need to provide a <Directory> section to allow access to
# the filesystem path.
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the target 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/ "/srv/http/cgi-bin/"
</IfModule>
<IfModule cgid_module>
# ScriptSock: On threaded servers, designate the path to the UNIX
# socket used to communicate with the CGI daemon of mod_cgid.
#Scriptsock cgisock
</IfModule>
# "/srv/http/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
<Directory "/srv/http/cgi-bin">
AllowOverride None
Options None
Require all granted
</Directory>
<IfModule mime_module>
# TypesConfig points to the file containing the list of mappings from
# filename extension to MIME-type.
TypesConfig conf/mime.types
# AddType allows you to add to or override the MIME configuration
# file specified in TypesConfig for specific file types.
#AddType application/x-gzip .tgz
# AddEncoding allows you to have certain browsers uncompress
# information on the fly. Note: Not all browsers support this.
#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 directive (see below)
# To use CGI scripts outside of ScriptAliased directories:
# (You will also need to add "ExecCGI" to the "Options" directive.)
#AddHandler cgi-script .cgi
# For type maps (negotiated resources):
#AddHandler type-map var
# Filters allow you to process content before it is sent to the client.
# To parse .shtml files for server-side includes (SSI):
# (You will also need to add "Includes" to the "Options" directive.)
#AddType text/html .shtml
#AddOutputFilter INCLUDES .shtml
</IfModule>
# The mod_mime_magic 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.
#MIMEMagicFile conf/magic
# Customizable error responses come in three flavors:
# 1) plain text 2) local redirects 3) external redirects
# Some examples:
#ErrorDocument 500 "The server made a boo boo."
#ErrorDocument 404 /missing.html
#ErrorDocument 404 "/cgi-bin/missing_handler.pl"
#ErrorDocument 402 http://www.example.com/subscription_info.html
# MaxRanges: Maximum number of Ranges in a request before
# returning the entire resource, or one of the special
# values 'default', 'none' or 'unlimited'.
# Default setting is to accept 200 Ranges.
#MaxRanges unlimited
# EnableMMAP and EnableSendfile: On systems that support it,
# memory-mapping or the sendfile syscall may be used to deliver
# files. This usually improves server performance, but must
# be turned off when serving from networked-mounted
# filesystems or if support for these functions is otherwise
# broken on your system.
# Defaults: EnableMMAP On, EnableSendfile Off
#EnableMMAP off
#EnableSendfile on
# Supplemental configuration
# The configuration files in the conf/extra/ directory can be
# included to add extra features or to modify the default configuration of
# the server, or you may simply copy their contents here and change as
# necessary.
# Server-pool management (MPM specific)
Include conf/extra/httpd-mpm.conf
# Multi-language error messages
Include conf/extra/httpd-multilang-errordoc.conf
# Fancy directory listings
Include conf/extra/httpd-autoindex.conf
# Language settings
Include conf/extra/httpd-languages.conf
# User home directories
Include conf/extra/httpd-userdir.conf
# Real-time info on requests and configuration
#Include conf/extra/httpd-info.conf
# Virtual hosts
#Include conf/extra/httpd-vhosts.conf
# Local access to the Apache HTTP Server Manual
#Include conf/extra/httpd-manual.conf
# Distributed authoring and versioning (WebDAV)
#Include conf/extra/httpd-dav.conf
# Various default settings
Include conf/extra/httpd-default.conf
# Include owncloud
Include /etc/httpd/conf/extra/owncloud.conf
Include conf/extra/php5_module.conf
# Configure mod_proxy_html to understand HTML4/XHTML1
<IfModule proxy_html_module>
Include conf/extra/proxy-html.conf
</IfModule>
# Secure (SSL/TLS) connections
Include conf/extra/httpd-ssl.conf
# Note: The following must must be present to support
# starting without SSL on platforms with no /dev/random equivalent
# but a statically compiled-in mod_ssl.
<IfModule ssl_module>
SSLRandomSeed startup builtin
SSLRandomSeed connect builtin
</IfModule>
# uncomment out the below to deal with user agents that deliberately
# violate open standards by misusing DNT (DNT *must* be a specific
# end-user choice)
#<IfModule setenvif_module>
#BrowserMatch "MSIE 10.0;" bad_DNT
#</IfModule>
#<IfModule headers_module>
#RequestHeader unset DNT env=bad_DNT
#</IfModule>
thanks!
Last edited by Carl Karl (2014-05-06 07:40:53)

OK, solved.
What I made wrong:
https://localhost leads to the apache page
https://localhost/owncloud leads to the owncloud page.
(Just as an information if there are other apache noobs like me...)

InitialContext lookup over HTTP using a full PROVIDER_URL (including path)

Hi,
We have a standalone Java JMS client application that is sending messages to a queue on a WebLogic (WLS 9.2 MP3) server. It uses the WLInitialContextFactory (WebLogic implementation of InitialContextFactory) class to look up the initial context over HTTP when making the connection to send messages to the queue.
This all works fine when the client connects directly to the server - i.e. supplies the address of the server as the PROVIDER_URL. However, in our infrastructure, we cannot connect directly from this client to the server; we need to go via a HTTP proxy.
In a basic configuration HTTP proxy we set the provider URL to be the address of the proxy server, with the proxy is configured to route all requests straight through to the WebLogic server. This configuration also works fine - the JMS client can send messages successfully.
Unfortunately, this basic proxy configuration is still not sufficient for our Production environment. Our production proxy "fronts" multiple servers, each one identified by the first portion of the URL. So, the proxy is be configured such that requests to "http://proxy/server1/test_request" will be routed on to "http://server1/test_request", whereas a request to "http://proxy/server2/test_request" will be routed to "http://server2/test_request". This configuration works fine for basic HTTP requests, to webpages etc.
However, when we try we use this mechanism with our JMS client over HTTP, it is not working. We set the provider URL on the client to "http://proxy/server1" in order to send a message to server1. However, we find that the WLInitialContextFactory class seems to be ignoring the final part of the URL ("server1") and still sending requests directly to the root proxy address of "http://proxy", so it doesn't work.
I appreciate that this can be viewed as a WebLogic specific implementation issue for their WLInitialContextFactory, and I've raised a query with their support people on this. From my own research however, it seems the behaviour of their factory is not different to most other implementations - i.e. the major implementations would all have this issue.
I'm wondering if anyone is aware of any implementations that would handle the situation I've described. If not (or otherwise!) is there something crazy about our approach that noone has catered for it?! It seems a reasonable situation to me, but maybe I'm missing something!
Any comments, advice, etc. would be greatly appreciated, thanks.
Regards,
Adrian
Edited by: AdrianFitz on 08-Apr-2010 12:21

Hi,
Thanks for the quick response. Would you mind providing a bit more detail on your suggestion, as am not 100% sure I understand it fully.
If I see what you are getting at, are you talking about configuring proxy settings on my client side, similar to how I have to configure my internet browser with proxy settings when accessing the internet from within my companys LAN?
If I'm interpreting that right, then I guess my use of the word proxy might be a bit inaccurate or lead to some confusion. What my orginal post described as a proxy should have been more accurately describes as a reverse proxy (acting primarily as a load balancer).
Ideally, other than changing the URL slightly, the client should be 'unaware' that it is going through a proxy at all.
Hope that clarifies somewhat, any further comments would be great! Thanks.
Regards,
Adrian

Trial SAN Certificate & Outlook Anywhere (RPC over HTTP) test fail

I am testing exchange 2013 where autodiscover pass while performing Outlook Anywhere (RPC over HTTP) connectivity test failed with invalid SSL certifiate . I am only using self certifiate .do any one idea if any CA provding SAN certificate trial basis.
Don't forget to mark helpful or answer
connect me :-
http://in.linkedin.com/in/satya11
http://facebook.com/satya.1000

Hi,
Agree with the above suggestion, ExRCA test cannot pass with self-signed certificate. And to ensure Outlook Anywhere work well , we need to install the self-signed certificate on all clients machines.
If you have any question, please feel free to let me know.
Thanks,
Angela Shi
TechNet Community Support

Loading a video over HTTP

I'm having problems loading a .3gp video over HTTP. I get the
following error message "Error preparing video for playing".
Everything else (xml data, images) loads nicely. I've tested
this with Nokia 6630 and N70, but with no luck.
If I transfer the files to my phone and load the video from
the memory card, it works just fine. Is there something I can do to
fix this?

Ciao
the defualt streaming protocol for Nokia is rtsp not http. So
it will not work an http call to a video.
Also using rtsp requires a streaming server, it's not enough
to place the video file on the server.
Other phone might use http for streaming.
Alessandro

AS2 over HTTPs

Hello!
Could anyone please help me with a AS2 configuration over HTTPs? We would like to send data to our partner.
When I am activating HTTPs I am getting the following screen:
Can anyone tell me which certificate is expected in the field "server certificate (keystore)"? Where should this certificate be stored?
Does anyone know where to find a documentation for AS2 over HTTPs?
Thank you!
Regards
Christian

Hi Christian
If you want to be able to see the actual filenames in the audit log, you can use this neat trick Unknown use case of DynamicConfigurationBean: Store file name to JMS header without mapping by Stefan Grube
For this, you need to use a two step DynamicConfigurationBean instead of one, and use the write/read operations instead of the insert operation.
Your processing sequence would be like this:
1) Module name - AF_Modules/DynamicConfigurationBean, Module key - getFilename
2) Module name - AF_Modules/DynamicConfigurationBean, Module key - setAS2Filename
And the configuration parameters:
1) getFilename parameters:
key.0           write http://sap.com/xi/XI/System/File FileName
value.0        module.filename
2) setAS2Filename parameters:
key.0           read http://seeburger.com/xi/AS2 dtAS2FileName
value.0        module.filename
This will write and read the filenames from the DynamicConfiguration fields and store them into the adapter framework module variable. Note that the value in "value.0" can be any arbitrary value but needs to have the prefix "module.", example "module.var1"
Using this approach, you would be able to see that actual value from the dynamic configuration header being stored into the module variable. An example below (note again that my scenario is in the reverse order, i.e. AS2 File Name --> FTP File Name)
Rgds
Eng Swee

Looking for suggestion for SOAP over HTTP API to Oracle 10G

I need to be able to write data to an oracle 10g database through a SOAP over HTTP connection. What is the suggest packages to do such an action.
Best regards,
Dale

I suspect the problem is that the actual communication between client & Oracle DB server is done on a random "high port"; not 1522.
The packets on the high port are not getting through the VPN.
What I have made work in the past is to use ssh tunneling.
Good Luck, you might need it.

Socket Connection Vs HTTP connection

I'm trying to get a better understanding of which to use to connect a midlet to a servlet.
Does anybody know of any advantages socket connections have over http connections i.e performance or anything you can think of? Or is there any reason http connections seem like better practice for this type of communication (servlet-midlet) besides portability across MIDP
I'll appreciate your opinions

HTTP is a particular kind of socket connection. If what you're doing is plain old HTTP, then HttpConnection is easier to use. If you need something more than HTTP, then use SocketConnection.

Outlook 2010 makes unexpected HTTPS connection for unrelated profile

I originally posted this in the Outlook forum, but was pointed here instead.
I have a number of different Outlook profiles, for unrelated Exchange accounts.
I recently noticed that a client's firewall log was showing unexpected failed logon attempts to port 443, from my IP, using my PC name and username. I eventually found that these connections corresponded to my starting Outlook 2010 on my PC, loading my usual
Outlook profile (unrelated to the client, although I do have another Outlook profile for this client's Exchange server.)
Recreating my usual profile didn't fix it. Eventually I created a test profile that contains just an empty PST file and the Fax service, and even opening this profile causes a failed HTTPS (presumably RPC over HTTPS) connection to the client.
Why would Outlook be making HTTPS connections (presumably RPC over HTTPS) to a server that isn't referenced in a profile? How can I remove such references?
Thanks.

This was marked as the answer, but it is not.
I use RPC-over-HTTP for all the accounts, so I can't disable it.
The question is why is Outlook attempting to connect to the server referenced in profile X when I'm connecting (successfully) to a entirely different server referenced in different profile Y?
Thanks.

Problem with loadMovie with IE over https connection

Similar Messages

Maybe you are looking for