web.config corrupt?

Jack of all master of none — Mon, 10 Apr 2006 11:08:49 GMT

It appears that my web.config under the services directory. Here it is. Can you help?

<?xml version="1.0" encoding="utf-8"?>

</sectionGroup>

</configSections>

</appSettings>

<!-- ASPACCELERATOR.NET CONFIGURATION (Comprehensive)

This configuration rule set determines if the client has requested a compressed response by

looking at the Accept-Encoding header or if it can accept it based on the User-Agent string

and other http headers. The settings below are then configured based on the request - refer

to the help for a complete description of what each option does and how it should be used.

setting default description

===================== ======= ===========================================================

compression false whether compression will be applied to the response output

level normal the compression level to use (low, normal or high)

suppression true whether the resposne will be suppressed (if possible)

algorithm deflate the compression algorithm to use (deflate or gzip)

sendPoweredBy true send an "X-Powered-By: ASPAccelerator/3.5" header

sendETag true send the cache header used for suppression

varyBy (empty) http headers to vary the content by (Vary-By http header)

throwLicenseException false whether to raise an error if a valid license is not found

-->

<!-- the default settings can be overridden as required. eg. the default compression

level to be used could be changed and suppression disabled:

-->

<!-- check for responses that we don't want to compress so we avoid any further content

negotiation and also do not add any Vary-By header (which would affect caching) -->

</when>

<!-- application-specific exceptions should be included here. eg:

</when>

-->

<!-- use the HTTP Accept-Encoding header to determine if the client will accept compressed content

and vary the cache by this header so different versions are stored in caches / proxies -->

</when>

</when>

<!-- neither compression method matched (or the header was absent). Strictly adhering

to the http standard means that the response should not be compressed but many

clients can still accept compressed content if it is sent to them -->

<!-- if the Accept-Encoding header wasn't sent then the browser may just be running in

HTTP/1.0 mode and so may not expect (or handle) a compressed response (esp. IE).

Unfortunately, we cannot just check the HTTP protocol of the request as it could

have come through a proxy server which has upgraded the request to HTTP/1.1 and

sending compressed content back to the client will produce scrambled text often

because the proxy does not send back the Content-Encoding header to tell the client

that the content is compressed (and the algorithm used)

If the client is running in HTTP/1.1 mode and *did* send the header but it didn't

reach us then it could have been masked by a local firewall that wants to filter

the content without having to uncompress it (eg. Norton Security). These typically

just rewrite characters in the header with '-' so we can look for this to decide

if the original client request was HTTP/1.1 if it has come through a proxy

(indicated by a Via or X-Forwarded-For header). -->

</if>

</if>

</when>

</if>

</if>

</when>

</otherwise>

</choose>

</if>

<!-- use the User Agent string to determine if the client will accept compressed content

and vary the cache by this header so different versions are stored in caches / proxies -->

</when>

</when>

</when>

</choose>

</when>

</when>

</if>

</when>

</choose>

</if>

</otherwise>

</choose>

<!-- due to the interaction between IE and the Adobe Acrobat plugin compression

can cause problems so disable it also, IE doesn't like compressed JavaScript

(when it's cached locally and then re-loaded) -->

</if>

</when>

</when>

</when>

</choose>

</if>

</when>

</choose>

<!-- any application specific settings for different compression levels should be defined here. eg:

</choose>

-->

</if>

</otherwise>

</choose>

</aspAccelerator>

</intesoft>

<system.web>

</httpModules>

<!-- DYNAMIC DEBUG COMPILATION

Set compilation debug="true" to insert debugging symbols (.pdb information)

into the compiled page. Because this creates a larger file that executes

more slowly, you should set this value to true only when debugging and to

false at all other times. For more information, refer to the documentation about

debugging ASP.NET files.

-->

<!-- CUSTOM ERROR MESSAGES

Set customErrors mode="On" or "RemoteOnly" to enable custom error messages, "Off" to disable.

Add <error> tags for each of the errors you want to handle.

"On" Always display custom (friendly) messages.

"Off" Always display detailed ASP.NET error information.

"RemoteOnly" Display custom (friendly) messages only to users not running

on the local Web server. This setting is recommended for security purposes, so

that you do not display application detail information to remote clients.

-->

<!-- AUTHENTICATION

This section sets the authentication policies of the application. Possible modes are "Windows",

"Forms", "Passport" and "None"

"None" No authentication is performed.

"Windows" IIS performs authentication (Basic, Digest, or Integrated Windows) according to

its settings for the application. Anonymous access must be disabled in IIS.

"Forms" You provide a custom form (Web page) for users to enter their credentials, and then

you authenticate them in your application. A user credential token is stored in a cookie.

"Passport" Authentication is performed via a centralized authentication service provided

by Microsoft that offers a single logon and core profile services for member sites.

-->

<!-- AUTHORIZATION

This section sets the authorization policies of the application. You can allow or deny access

to application resources by user or role. Wildcards: "*" mean everyone, "?" means anonymous

(unauthenticated) users.

-->

<!-- <allow users="[comma separated list of users]"

roles="[comma separated list of roles]"/>

<deny users="[comma separated list of users]"

roles="[comma separated list of roles]"/>

-->

</authorization>

<!-- APPLICATION-LEVEL TRACE LOGGING

Application-level tracing enables trace log output for every page within an application.

Set trace enabled="true" to enable application trace logging. If pageOutput="true", the

trace information will be displayed at the bottom of each page. Otherwise, you can view the

application trace log by browsing the "trace.axd" page from your web application

root.

-->

<!-- SESSION STATE SETTINGS

By default ASP.NET uses cookies to identify which requests belong to a particular session.

If cookies are not available, a session can be tracked by adding a session identifier to the URL.

To disable cookies, set sessionState cookieless="true".

-->

<!-- GLOBALIZATION

This section sets the globalization settings of the application.

-->

<?dd name="HttpGet" />

</protocols>

</soapExtensionTypes>

</webServices>

</system.web>

<microsoft.web.services2>

</security>

</messaging>

<input>

</input>

</output>

</filters>

</microsoft.web.services2>

</configuration>

Calyx Software Message Board / Point Data Server (PDS) / Point Data Server (PDS) / web.config corrupt? / Latest Posts

RE: web.config corrupt?

RE: web.config corrupt?

You are not authorized to view this page

HTTP Error 403 - Forbidden
Internet Explorer

RE: web.config corrupt?

RE: web.config corrupt?

web.config corrupt?

You are not authorized to view this page
You might not have permission to view this directory or page using the credentials you supplied.
If you believe you should be able to view this directory or page, please try to contact the Web site by using any e-mail address or phone number that may be listed on the 127.0.0.1 home page. You can click Search to look for information on the Internet. HTTP Error 403 - Forbidden Internet Explorer

Calyx Software Message Board / Point Data Server (PDS) / Point Data Server (PDS) / web.config corrupt? / Latest Posts

RE: web.config corrupt?

RE: web.config corrupt?

You are not authorized to view this page

HTTP Error 403 - Forbidden Internet Explorer

RE: web.config corrupt?

RE: web.config corrupt?

web.config corrupt?

HTTP Error 403 - Forbidden
Internet Explorer