I need to change the alfresco explorer and share url using proxy. How to change the url?
My current url is http://System1:8080/alfresco, http://System1:8080/share
I need to change to http://kroxx, http://wiks
You need to configure both servers to produce the correct links. This configuration should go in your alfresco-global.properties, making sure that each WAR file accesses its relevant configuration entries:
alfresco.context=
alfresco.host=kroxx
alfresco.port=80
alfresco.protocol=http
share.context=
share.host=wikis
share.port=80
share.protocol=http
You most likely need also to change your Share configuration in order for CMIS to properly produce links to your public Alfresco URLs. The following goes to your share-config-custom.xml:
<alfresco-config>
<config evaluator="string-compare" condition="Server">
<server>
<scheme>http</scheme>
<hostname>kroxx</hostname>
<port>80</port>
</server>
</config>
</alfresco-config>
Related
When I try to update the contact information for geoserver global settings using https://127.0.0.1:8080/geoserver/rest/settings doesn't work. When I try to update below info using the above call
<global>
<settings>
<contact>
<address>test</address>
<addressCity>Hyderabad</addressCity>
<addressCountry>India</addressCountry>
</contact>
</settings>
</global>
It resets all the details from contact info and put only the above three fields. Is there any attribute or a way to make it work as expected. My requirement is to update only the fields sent through the request and keeping the remaining fields unchanged.
Thanks in advance.
You need to GET all the contact info as an XML or JSON file and then make the changes you need and then POST the changed file back to GeoServer.
with maven you can easily specify settings.xml location, e.g:
mvn -s custom/dir/settings.xml package
Is there a similiar way to specify custom security-settings.xml?
The reasoning behind this is simple: to easily distribute it via a local repository. Now, security is NOT a concern - it's all on the intranet.
This was requested as MNG-4853. Although not implemented directly, a workaround is suggested:
I've verified that -Dsettings.security=path/to/security-settings.xml works
As detailed in the announcement blog post, you can also use the master password relocation feature. Write an ~/.m2/security-settings.xml file with a redirection in it:
<settingsSecurity>
<relocation>/Volumes/mySecureUsb/secret/settings-security.xml</relocation>
</settingsSecurity>
Having multiple development stages, I'd like to keep some magento configurations in a file, and not in the database, so i can have my development version and the production version in sync.
So i need to put in a different place the "base url", that is not the database, because I'd like to export it from production to development
is it possible?
It's possible:
<default>
<web>
<unsecure>
<base_url>https://foo.dev/</base_url>
</unsecure>
<secure>
<base_url>https://foo.dev/</base_url>
</secure>
</web>
</default>
<websites>
<ws_code>
<web>
<unsecure>
<base_url>http://ws.foo.dev/</base_url>
</unsecure>
<secure>
<base_url>https://ws.foo.dev/</base_url>
</secure>
</web>
</ws_code>
</websites>
<stores>
<store_code>
<web>
<unsecure>
<base_url>http://store.foo.dev/</base_url>
</unsecure>
<secure>
<base_url>https://store.foo.dev/</base_url>
</secure>
</web>
</store_code>
</stores>
However if anyone ever saves (or has saved) the System > Configuration > Web section in the admin, the values in your config file for that scope will not apply.
There are a couple of strategies for protecting your entries
Use the file-based config approach and disable access to the Web section via admin user roles (for all users). Caveat: you'll need to provide all of the configuration options in your config.
Use setup scripts (PHP) to write the base_url entries to the core_config_data table, and protect them from being overwritten via an observer configured under the adminhtml event area for the core_config_data_save_before event.
You could also combine the observer protection from strategy #2 with the file-based config from strategy #1.
Ive been trying a few days to activate the FriendlyService in exo-platfom 3.5.x but have been unsuccessful so far.
In the section:
administration > management
There is a service called Friendly Service which allows eXo to rewrite a request URL to another URL (in a more readable format). However, this service is inactivated.
Can someone tell me how activate it?
1.When starting server, you need to enable the profile 'friendly':
Example: ./start_eXo.sh -Dfriendly
2.When registering FriendlyService, you need to provide parameter enable as true:
<component>
<key>org.exoplatform.services.wcm.friendly.FriendlyService</key>
<jmx-name>exo-service:type=FriendlyService</jmx-name>
<type>org.exoplatform.services.wcm.friendly.impl.FriendlyServiceImpl</type>
<init-params>
<value-param>
<name>enabled</name>
<value>true</value>
</value-param>
</init-params>
</component>
Hope it helps..
So in IIS 7 if there is no specific MIME definition for a certain extension, it will refuse to serve it (404) even if you can see it in a directory listing. I'm sure this is a fairly known issue, but is there a way to wildcard or set a default action for unknown file types? I want everything to be offered for download by default like with every other webserver I've used.
Add a new MIME type for files of extension * with a type of application/octet-stream. This will provide a default MIME type for all files that don't have one and bypass the blocking.
The risk, however, is you end up sharing your confidential database, configuration files and whatnot, so make sure you know what you are doing before you open your server to all downloads.
+1 #H2Professor
But here's the code (in this case web.config for IIS 7+):
<configuration>
<system.webServer>
<staticContent>
<mimeMap fileExtension="*" mimeType="application/octet-stream" />
</staticContent>
</system.webServer>
</configuration>
I believe you just need to edit your website in Internet Information Services Manager and double click the Request Filtering icon and edit it however you like there.
The mime type configuration does not allow/disallow downloading files; it just tells IIS what to throw in the header when you do download it.