Menu
▾
▴
webassembletool-users — ESIGate user list
You can subscribe to this list here.
| 2009 |
Jan
|
Feb
|
Mar
(4) |
Apr
|
May
|
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(6) |
Dec
(4) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(3) |
Jun
|
Jul
|
Aug
(2) |
Sep
|
Oct
(1) |
Nov
(1) |
Dec
(1) |
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(1) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2012 |
Jan
(1) |
Feb
|
Mar
(6) |
Apr
(1) |
May
|
Jun
|
Jul
(4) |
Aug
|
Sep
|
Oct
(8) |
Nov
|
Dec
(1) |
| 2013 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
(9) |
Jun
(2) |
Jul
(5) |
Aug
|
Sep
|
Oct
(2) |
Nov
|
Dec
|
| 2014 |
Jan
(1) |
Feb
|
Mar
|
Apr
(7) |
May
(6) |
Jun
(7) |
Jul
|
Aug
|
Sep
(5) |
Oct
(29) |
Nov
(14) |
Dec
(10) |
| 2015 |
Jan
|
Feb
(4) |
Mar
(8) |
Apr
|
May
|
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
(6) |
Nov
|
Dec
(2) |
| 2016 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(21) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Nicolas R. <nic...@gm...> - 2014-12-04 07:54:51
|
Hi Volker, I agree with Alexis and François-Xavier. A few additional comments on esigate-server : > > 2) esigate-server is a pre-packaged version of the EsiGate filter deployed inside a Jetty server. It is easy to run and you have nothing to install, that is why it is often used in development. I think you could safely use it in production but it still lacks some features like init scripts (but this is currently in progress) so you would have a little work to setup everything In the 4.X branch you cannot configure provider mappings in esigate-server. Threads, max connections, … are also not configurable. This is why it is not suited for real projects. In the 5.x branch, these issues are fixed. It can be used the same way than esigate-war, but this setup is less tested than the standard one. The whole 5.X branch is still in development. It is quite stable, but configuration/behavior may slightly change before release. Using it during development ensure there are no upcoming breaking changes for your project. If you find any bug, feel free to open issues on github. -- Nicolas |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-12-03 21:08:47
|
Hi Volker, Sorry for the mails in French on the mailing list. We are talking about 3 different things here: 1) esigate-servlet is the artifact that contains the main EsiGate filter that you deploy in a web application. Then you deploy the web application on any servlet container like Tomcat, Websphere, Weblogic, Jetty... This is the recommended and most common way to run EsiGate in production. 2) esigate-server is a pre-packaged version of the EsiGate filter deployed inside a Jetty server. It is easy to run and you have nothing to install, that is why it is often used in development. I think you could safely use it in production but it still lacks some features like init scripts (but this is currently in progress <https://github.com/esigate/esigate/issues/61>) so you would have a little work to setup everything 3) ServletExtension is a new feature of version 5 (that is also included in esigate-servlet artifact by the way) that replaces the http requests by local includes <https://docs.oracle.com/javaee/6/api/javax/servlet/RequestDispatcher.html#include(javax.servlet.ServletRequest, javax.servlet.ServletResponse)>. So you can use this extension when you want to include some contents from inside the application where EsiGate runs or from a webapp that is deployed on the same servlet container instance. In this particular case skipping the network calls may make your architecture simpler and improve the performance. Of course if the applications you aggregate with EsiGate are deployed on another machine or are php on .net application, you cannot use this extension. I hope my explanation is clear. 2014-12-03 19:05 GMT+01:00 Volker Kümmer <vol...@gm...>: > "L'extension org.esigate.servlet.ServletExtension est une nouveauté de la > version 5" > > so the filter is not working correctly in the moment and the stand alone > server is said to be for development (see: > http://www.esigate.org/esigate-server/index.html) only. > Can you please explain to me, what is the recommended way to run an > ESIGate installation for production is? > > kind regadrs > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: alexis t. <ale...@gm...> - 2014-12-03 21:08:44
|
The best way is to deploy esigate in a tomcat server, with / context path (ROOT.war). It will act as a reverse proxy, and is the most frequently use case. Standalone server is just an embedded jetty with esigate.war, but is less tested. ServletExtension is an optimisation to minimise http traffic by including local tomcat resources. @dev team : We have to clarify the documentation. Le 3 déc. 2014 19:05, "Volker Kümmer" <vol...@gm...> a écrit : > "L'extension org.esigate.servlet.ServletExtension est une nouveauté de la > version 5" > > so the filter is not working correctly in the moment and the stand alone > server is said to be for development (see: > http://www.esigate.org/esigate-server/index.html) only. > Can you please explain to me, what is the recommended way to run an > ESIGate installation for production is? > > kind regadrs > > > ------------------------------------------------------------------------------ > Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server > from Actuate! Instantly Supercharge Your Business Reports and Dashboards > with Interactivity, Sharing, Native Excel Exports, App Integration & more > Get technology previously reserved for billion-dollar corporations, FREE > > http://pubads.g.doubleclick.net/gampad/clk?id=164703151&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Volker K. <vol...@gm...> - 2014-12-03 18:05:31
|
"L'extension org.esigate.servlet.ServletExtension est une nouveauté de la version 5" so the filter is not working correctly in the moment and the stand alone server is said to be for development (see: http://www.esigate.org/esigate-server/index.html) only. Can you please explain to me, what is the recommended way to run an ESIGate installation for production is? kind regadrs |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-12-02 16:32:26
|
Bonjour,
L'extension org.esigate.servlet.ServletExtension est une nouveauté de la
version 5, elle permet de remplacer les appels http par des includes en
local dans l'application ou des includes en cross-context quand les
applications sont des applications java déployées sur le même serveur
d'application (ce qui peut améliorer les performances).
Si j'ai bien compris dans votre cas les deux applications sont sur deux
instances WAS distinctes. Donc si on demande à EsiGate de chercher la page
en local sur le serveur Websphere Commerce, il obtient une erreur 404.
En retirant cette extension ça devrait fonctionner.
Le 2 décembre 2014 15:54, Nicolas Toquet <nic...@al...> a
écrit :
> En pièce jointe l'exception renvoyée par notre serveur
>
> Cordialement
> Nicolas TOQUET
>
> Le 2 décembre 2014 15:38, Nicolas Toquet <nic...@al...> a
> écrit :
>
> Bonjour,
>>
>> Nous rencontrons quelques soucis avec EsiGate.
>> Nous avons déjà utilisé les librairies lors de précédent projets. Il
>> s'agissait de la version 4. Cela fonctionnait bien
>> Nous essayons d'intégrer la dernière version 5.0 beta 2.
>> Voici notre configuration :
>>
>> un serveur local Websphere commerce (maître)
>> un serveur local (8080) Magnolia CMS (esclave)
>>
>> Nous devons intégrer des pages de notre cms dans la webapp websphere
>> commerce
>> Voici où nous en sommes :
>>
>> - Installation des lib dans WC/lib/esigate/*.jar
>> - Ajout d'un fichier esigate.properties dans WC/properties/
>> - Dans le fichier properties ajout des ligne suivantes :
>> - local.remoteUrlBase=http://localhost:8080/magnoliaPublic/
>> -
>> local.extensions=org.esigate.servlet.ServletExtension,org.esigate.extension.Esi
>> - local.mappings=*
>> - Ajout du filter et filter mapping dans le fichier web.xml de notre
>> projet (websphere)
>> - Tests :
>> - afficher un contenu magnolia : <esi:include src="
>> http://localhost:8080/magnoliaPublic/test-hello-world" /> *OK*
>> - afficher une variable
>> : <esi:vars>$(PROVIDER{local})/test-hello-world</esi:vars> *OK
>> renvoie *http://localhost:8080/magnoliaPublic/test-hello-world
>> - Afficher un contenu en utilisant le provider : <esi:include
>> src="$(PROVIDER{local})/test-hello-world" /> *KO (*/test-hello-world
>> not found pour résumer l'exception)
>>
>> Je n'ai pas trouvé à l'heure actuelle de solution à mon problème.
>> J'imagine que le esi:include est capable d'interpréter les variables mais
>> il semble que le $(PROVIDER{local}) n'est pas reconnu.
>>
>> Avez-vous des pistes à nous indiquer pour que l'on puisse avancer sur ce
>> sujet ?
>>
>>
>> Nicolas TOQUET
>>
>>
>>
>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=157005751&iu=/4140/ostg.clktrk
> _______________________________________________
> Webassembletool-users mailing list
> Web...@li...
> https://lists.sourceforge.net/lists/listinfo/webassembletool-users
>
>
|
|
From: Nicolas T. <nic...@al...> - 2014-12-02 15:05:06
|
Bonjour,
Nous rencontrons quelques soucis avec EsiGate.
Nous avons déjà utilisé les librairies lors de précédent projets. Il
s'agissait de la version 4. Cela fonctionnait bien
Nous essayons d'intégrer la dernière version 5.0 beta 2.
Voici notre configuration :
un serveur local Websphere commerce (maître)
un serveur local (8080) Magnolia CMS (esclave)
Nous devons intégrer des pages de notre cms dans la webapp websphere
commerce
Voici où nous en sommes :
- Installation des lib dans WC/lib/esigate/*.jar
- Ajout d'un fichier esigate.properties dans WC/properties/
- Dans le fichier properties ajout des ligne suivantes :
- local.remoteUrlBase=http://localhost:8080/magnoliaPublic/
-
local.extensions=org.esigate.servlet.ServletExtension,org.esigate.extension.Esi
- local.mappings=*
- Ajout du filter et filter mapping dans le fichier web.xml de notre
projet (websphere)
- Tests :
- afficher un contenu magnolia : <esi:include src="
http://localhost:8080/magnoliaPublic/test-hello-world" /> *OK*
- afficher une variable
: <esi:vars>$(PROVIDER{local})/test-hello-world</esi:vars> *OK
renvoie *http://localhost:8080/magnoliaPublic/test-hello-world
- Afficher un contenu en utilisant le provider : <esi:include
src="$(PROVIDER{local})/test-hello-world" /> *KO (*/test-hello-world
not found pour résumer l'exception)
Je n'ai pas trouvé à l'heure actuelle de solution à mon problème.
J'imagine que le esi:include est capable d'interpréter les variables mais
il semble que le $(PROVIDER{local}) n'est pas reconnu.
Avez-vous des pistes à nous indiquer pour que l'on puisse avancer sur ce
sujet ?
Nicolas TOQUET
|
|
From: Nicolas T. <nic...@al...> - 2014-12-02 14:54:55
|
[02/12/14 15:48:08:819 CET] FFDC Exception:com.ibm.ws.webcontainer.webapp.WebAppErrorReport SourceId:com.ibm.ws.webcontainer.servlet.FilterProxyServlet.dispatch ProbeId:312 Reporter:com.ibm.ws.webcontainer.servlet.FilterProxyServlet@28342834 com.ibm.ws.webcontainer.webapp.WebAppErrorReport: SRVE0190E: Fichier non trouvé : /test-hello-world at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:991) at com.ibm.ws.webcontainer.webapp.WebAppRequestDispatcher.forward(WebAppRequestDispatcher.java:374) at org.esigate.servlet.ServletExtension.event(ServletExtension.java:108) at org.esigate.events.EventManager.fire(EventManager.java:162) at org.esigate.events.EventManager.fire(EventManager.java:143) at org.esigate.http.ProxyingHttpClientBuilder$1.execute(ProxyingHttpClientBuilder.java:94) at org.esigate.cache.CacheAdapter$2.execute(CacheAdapter.java:145) at org.apache.http.impl.client.cache.CachingExec.callBackend(CachingExec.java:576) at org.apache.http.impl.client.cache.CachingExec.handleCacheMiss(CachingExec.java:344) at org.apache.http.impl.client.cache.CachingExec.execute(CachingExec.java:263) at org.esigate.cache.CacheAdapter$1.execute(CacheAdapter.java:83) at org.apache.http.impl.execchain.ProtocolExec.execute(ProtocolExec.java:195) at org.apache.http.impl.execchain.RetryExec.execute(RetryExec.java:85) at org.apache.http.impl.execchain.RedirectExec.execute(RedirectExec.java:108) at org.apache.http.impl.client.InternalHttpClient.doExecute(InternalHttpClient.java:186) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:72) at org.apache.http.impl.client.CloseableHttpClient.execute(CloseableHttpClient.java:57) at org.esigate.http.HttpClientRequestExecutor.execute(HttpClientRequestExecutor.java:292) at org.esigate.http.HttpClientRequestExecutor.createAndExecuteRequest(HttpClientRequestExecutor.java:322) at org.esigate.Driver.render(Driver.java:165) at org.esigate.esi.IncludeElement.processPage(IncludeElement.java:211) at org.esigate.esi.IncludeElement.onTagEnd(IncludeElement.java:82) at org.esigate.parser.ParserContextImpl.endElement(ParserContextImpl.java:84) at org.esigate.parser.Parser.parse(Parser.java:84) at org.esigate.esi.EsiRenderer.render(EsiRenderer.java:121) at org.esigate.Driver.performRendering(Driver.java:367) at org.esigate.Driver.performRendering(Driver.java:326) at org.esigate.Driver.proxy(Driver.java:262) at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:66) at com.ibm.ws.webcontainer.filter.FilterInstanceWrapper.doFilter(FilterInstanceWrapper.java:190) at com.ibm.ws.webcontainer.filter.WebAppFilterChain.doFilter(WebAppFilterChain.java:125) at com.ibm.ws.webcontainer.filter.WebAppFilterChain._doFilter(WebAppFilterChain.java:80) at com.ibm.ws.webcontainer.filter.WebAppFilterManager.doFilter(WebAppFilterManager.java:908) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:939) at com.ibm.ws.webcontainer.servlet.ServletWrapper.handleRequest(ServletWrapper.java:507) at com.ibm.ws.webcontainer.servlet.ServletWrapperImpl.handleRequest(ServletWrapperImpl.java:181) at com.ibm.ws.webcontainer.webapp.WebApp.handleRequest(WebApp.java:3954) at com.ibm.ws.webcontainer.webapp.WebGroup.handleRequest(WebGroup.java:276) at com.ibm.ws.webcontainer.WebContainer.handleRequest(WebContainer.java:945) at com.ibm.ws.webcontainer.WSWebContainer.handleRequest(WSWebContainer.java:1592) at com.ibm.ws.webcontainer.channel.WCChannelLink.ready(WCChannelLink.java:191) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleDiscrimination(HttpInboundLink.java:453) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.handleNewRequest(HttpInboundLink.java:515) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.processRequest(HttpInboundLink.java:306) at com.ibm.ws.http.channel.inbound.impl.HttpInboundLink.ready(HttpInboundLink.java:277) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.sendToDiscriminators(NewConnectionInitialReadCallback.java:214) at com.ibm.ws.tcp.channel.impl.NewConnectionInitialReadCallback.complete(NewConnectionInitialReadCallback.java:113) at com.ibm.ws.tcp.channel.impl.AioReadCompletionListener.futureCompleted(AioReadCompletionListener.java:175) at com.ibm.io.async.AbstractAsyncFuture.invokeCallback(AbstractAsyncFuture.java:217) at com.ibm.io.async.AsyncChannelFuture.fireCompletionActions(AsyncChannelFuture.java:161) at com.ibm.io.async.AsyncFuture.completed(AsyncFuture.java:138) at com.ibm.io.async.ResultHandler.complete(ResultHandler.java:204) at com.ibm.io.async.ResultHandler.runEventProcessingLoop(ResultHandler.java:775) at com.ibm.io.async.ResultHandler$2.run(ResultHandler.java:905) at com.ibm.ws.util.ThreadPool$Worker.run(ThreadPool.java:1660) Caused by: java.io.FileNotFoundException: /test-hello-world at com.ibm.ws.webcontainer.extension.DefaultExtensionProcessor.handleRequest(DefaultExtensionProcessor.java:590) ... 54 more Reporter BEGIN:com.ibm.ws.webcontainer.servlet.FilterProxyServlet@28342834 javax.servlet.GenericServlet::LSTRING_FILE:javax.servlet.LocalStrings javax.servlet.GenericServlet::lStrings BEGIN:java.util.PropertyResourceBundle@407c407c java.util.PropertyResourceBundle@407c407c END:java.util.PropertyResourceBundle@407c407c javax.servlet.GenericServlet::config BEGIN:com.ibm.ws.webcontainer.servlet.ServletConfigImpl@1f651f65 com.ibm.ws.container.BaseConfiguration::_id:InternalServlet_FilterProxyServlet com.ibm.ws.container.BaseConfiguration::name:null com.ibm.ws.container.BaseConfiguration::_attributes:null com.ibm.ws.webcontainer.servlet.TargetConfig::initParams:null com.ibm.ws.webcontainer.servlet.TargetConfig::isJsp:false com.ibm.ws.webcontainer.servlet.TargetConfig::fileName:null com.ibm.ws.webcontainer.servlet.TargetConfig::displayName:FilterProxyServlet com.ibm.ws.webcontainer.servlet.TargetConfig::name:null com.ibm.ws.webcontainer.servlet.TargetConfig::description:null com.ibm.ws.webcontainer.servlet.TargetConfig::smallIcon:null com.ibm.ws.webcontainer.servlet.TargetConfig::largeIcon:null com.ibm.ws.webcontainer.servlet.ServletConfig::servletName:FilterProxyServlet com.ibm.ws.webcontainer.servlet.ServletConfig::className:com.ibm.ws.webcontainer.servlet.FilterProxyServlet com.ibm.ws.webcontainer.servlet.ServletConfig::mappings:null com.ibm.ws.webcontainer.servlet.ServletConfig::startUpWeight:null com.ibm.ws.webcontainer.servlet.ServletConfig::DEFAULT_STARTUP:-1 com.ibm.ws.webcontainer.servlet.ServletConfig::isCachingEnabled:true com.ibm.ws.webcontainer.servlet.ServletConfig::isStatisticsEnabled:true com.ibm.ws.webcontainer.servlet.ServletConfig::context BEGIN:com.ibm.wsspi.webcontainer.facade.ServletContextFacade@3a023a02 com.ibm.wsspi.webcontainer.facade.ServletContextFacade::context:com.ibm.ws.webcontainer.webapp.WebAppImpl@3d6b3d6b depth limit reached END:com.ibm.wsspi.webcontainer.facade.ServletContextFacade@3a023a02 com.ibm.ws.webcontainer.servlet.ServletConfig::isInternal:false com.ibm.ws.webcontainer.servlet.ServletConfig::metaData BEGIN:com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl@1f9a1f9a com.ibm.ws.runtime.metadata.MetaDataImpl::tc:com.ibm.ejs.ras.TraceComponent@2bce2bce depth limit reached com.ibm.ws.runtime.metadata.MetaDataImpl::slots:[Ljava.lang.Object;@1fa61fa6 depth limit reached com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::securityMetaData:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::logger:com.ibm.wsspi.webcontainer.logging.WebContainerLogger@1b381b38 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::CLASS_NAME:com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_name:InternalServlet_FilterProxyServlet com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_implementationClass:com.ibm.ws.webcontainer.servlet.FilterProxyServlet com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_javaColonContext:javax.naming.InitialContext@1b291b29 depth limit reached com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_mmd:com.ibm.ws.webcontainer.metadata.WebModuleMetaDataImpl@17021702 depth limit reached com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_j2eeName:com.ibm.ejs.csi.J2EENameImpl@1f711f71 depth limit reached com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_webComponentType:1 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_webComponentVersion:2.5 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_resRefList:com.ibm.ejs.csi.ResRefListImpl@16d516d5 depth limit reached com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_localTran:com.ibm.ejs.csi.LocalTranConfigDataImpl@54605460 depth limit reached com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_globalTran:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_webGlobalTran:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_jns:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_webComponentDescription:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_webComponentInitParameters:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_pageList:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::_state:0 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::config:com.ibm.ws.webcontainer.servlet.ServletConfigImpl@1f651f65 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::VALID:0 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::DESTROYED:1 com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::lock:java.lang.Object@1faa1faa com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::invocationCallbacksContext:null com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl::invocationCallbacksStorage:com.ibm.ws.util.WSThreadLocal@3ae43ae4 depth limit reached END:com.ibm.ws.webcontainer.metadata.WebComponentMetaDataImpl@1f9a1f9a END:com.ibm.ws.webcontainer.servlet.ServletConfigImpl@1f651f65 javax.servlet.http.HttpServlet::METHOD_DELETE:DELETE javax.servlet.http.HttpServlet::METHOD_HEAD:HEAD javax.servlet.http.HttpServlet::METHOD_GET:GET javax.servlet.http.HttpServlet::METHOD_OPTIONS:OPTIONS javax.servlet.http.HttpServlet::METHOD_POST:POST javax.servlet.http.HttpServlet::METHOD_PUT:PUT javax.servlet.http.HttpServlet::METHOD_TRACE:TRACE javax.servlet.http.HttpServlet::HEADER_IFMODSINCE:If-Modified-Since javax.servlet.http.HttpServlet::HEADER_LASTMOD:Last-Modified javax.servlet.http.HttpServlet::LSTRING_FILE:javax.servlet.http.LocalStrings javax.servlet.http.HttpServlet::lStrings BEGIN:java.util.PropertyResourceBundle@79517951 java.util.PropertyResourceBundle@79517951 END:java.util.PropertyResourceBundle@79517951 javax.servlet.http.HttpServlet::class$javax$servlet$http$HttpServlet:null com.ibm.ws.webcontainer.servlet.FilterProxyServlet::serialVersionUID:3544394690804857138 com.ibm.ws.webcontainer.servlet.FilterProxyServlet::logger:com.ibm.wsspi.webcontainer.logging.WebContainerLogger@69706970 com.ibm.ws.webcontainer.servlet.FilterProxyServlet::CLASS_NAME:com.ibm.ws.webcontainer.servlet.FilterProxyServlet com.ibm.ws.webcontainer.servlet.FilterProxyServlet::nls BEGIN:com.ibm.ejs.sm.client.ui.NLS@54175417 com.ibm.ejs.sm.client.ui.NLS::tc BEGIN:com.ibm.ejs.ras.TraceComponent@66866686 com.ibm.ejs.ras.TraceElement::ivLevel:10 com.ibm.ejs.ras.TraceElement::ivName:com.ibm.ejs.sm.client.ui.NLS com.ibm.ejs.ras.TraceElement::ivDebugEnabled:false com.ibm.ejs.ras.TraceElement::ivEventEnabled:false com.ibm.ejs.ras.TraceElement::ivEntryEnabled:false com.ibm.ejs.ras.TraceElement::ivDetailEnabled:false com.ibm.ejs.ras.TraceElement::ivConfigEnabled:false com.ibm.ejs.ras.TraceElement::ivInfoEnabled:true com.ibm.ejs.ras.TraceElement::ivServiceEnabled:true com.ibm.ejs.ras.TraceElement::ivWarningEnabled:true com.ibm.ejs.ras.TraceElement::ivErrorEnabled:true com.ibm.ejs.ras.TraceElement::ivFatalEnabled:true com.ibm.ejs.ras.TraceComponent::defaultMessageFile:com.ibm.ejs.resources.seriousMessages com.ibm.ejs.ras.TraceComponent::EXTENSION_NAME_DPID:DiagnosticProvider com.ibm.ejs.ras.TraceComponent::ivDumpEnabled:false com.ibm.ejs.ras.TraceComponent::ivResourceBundleName:com.ibm.ejs.resources.seriousMessages com.ibm.ejs.ras.TraceComponent::ivLogger:null com.ibm.ejs.ras.TraceComponent::ivDiagnosticProviderID:null com.ibm.ejs.ras.TraceComponent::anyTracingEnabled:true END:com.ibm.ejs.ras.TraceComponent@66866686 com.ibm.ejs.sm.client.ui.NLS::messages:null com.ibm.ejs.sm.client.ui.NLS::baseClassPackage:com.ibm.ejs.resources com.ibm.ejs.sm.client.ui.NLS::bundleName:com.ibm.ws.webcontainer.resources.Messages com.ibm.ejs.sm.client.ui.NLS::bundle BEGIN:com.ibm.ws.webcontainer.resources.Messages_fr@2fa02fa com.ibm.ws.webcontainer.resources.Messages_fr@2fa02fa com.ibm.ws.webcontainer.resources.Messages_fr::resources:[[Ljava.lang.Object;@8ea08ea depth limit reached END:com.ibm.ws.webcontainer.resources.Messages_fr@2fa02fa END:com.ibm.ejs.sm.client.ui.NLS@54175417 END:com.ibm.ws.webcontainer.servlet.FilterProxyServlet@28342834 |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-11-20 10:13:03
|
Bonjour, Ca m'intéresse d'avoir le code. C'est spécifique au projet ou générique et potentiellement open source ? Je ne connais pas bien la esigate-portlet, ça fait la même chose ? C'est complémentaire ? Ca n'a rien à voir ? Le 18 novembre 2014 11:59, <wil...@gm...> a écrit : > Merci pour vos retour. > > Finalement je suis partie sur le même fonctionnement que l'implémentation > de Jahia. > > J'ai créé deux nouvelles classes dans ESIGate : > - une nouvelle extension qui prend en paramètre une URL Liferay qui sert > de template de page et un fragment qui sera remplacé par le contenu de > l'application agrégée, > - un nouveau renderer qui ajoute un tag "esi:include" ayant pour source > l'URL Liferay et qui contient une balise "esi:replace" pour remplacer le > fragment par le contenu de mon "remoteUrlBase". > > Cela répond parfaitement à mon besoin. > > Si cela vous intéresse, je peux vous envoyer le code source. > > William > > > Le 15 novembre 2014 22:56, Francois-Xavier Bonnet < > fra...@ce...> a écrit : > > Bonjour, >> >> Pour intégrer une application et qu'elle soit navigable, il faut faire >> dans l'autre sens : c'est l'application qui doit utiliser les pages Liferay >> comme des templates en utilisant des tags <esi:include> et <esi:replace>. >> Ainsi c'est l'application qui a le contrôle de la navigation. C'est >> précisément l'exemple qui est décrit dans ce tutorial : >> http://www.esigate.org/quickstart.html >> >> Dans le cas de Liferay il y a aussi une solution expérimentale qui permet >> d'intégrer l'application sous forme d'une portlet : >> https://github.com/Smile-SA/esigate-portlet >> >> Le 13 novembre 2014 14:13, William Dupuis <wil...@gm...> a >> écrit : >> >>> Bonjour, >>> Je fais appel à vous car je n'arrive pas à comprendre comment inclure >>> une application dans Liferay via un serveur ESIGate dédié. >>> >>> Voici mon besoin : >>> - Inclure sur une page Liferay une application et pouvoir naviguer dans >>> cette application tout en restant dans ma page Liferay. >>> >>> Pour faire cela, j'ai 3 serveurs Tomcat : >>> - 1 serveur ESIGate accessible via l'URL : >>> http://test.local.env/esigate/ >>> - 1 serveur Liferay accessible via l'URL : http://test.local.env/ >>> - 1 serveur Tomcat avec mon appli accessible via l'URL : >>> http://serveur-appli:8080/appli/ >>> L'accès à mon application se fera exclusivement via ESIGate. >>> >>> Pour le moment, j'ai testé en ajoutant dans ma page Liferay, un tag >>> esi:include : >>> <esi:include src="http://serveur-appli:8080/appli/" /> >>> >>> L'inclusion se fait bien mais je ne peux pas naviguer dans mon >>> application en restant dans ma page Liferay. >>> J'ai également pas mal de problème de ré-écriture d'URL pour les >>> fichiers statiques. >>> Vous trouverez en pièce-jointe mon fichier esigate.properties. >>> >>> Pour accéder à ma page Liferay, j'utilise l'URL : >>> http://test.local.env/esigate/private/liferay/mapageliferay >>> >>> Je pense que ma stratégie n'est pas la bonne. >>> En regardant en détail comment Jahia a intégré ESIGate dans leur >>> solution, j'ai vu qu'ils ont créé une nouvelle Extension afin de générer un >>> tag esi:include. >>> Dans les paramètres du provider, ils indiquent l'URL source (donc pour >>> moi mon URL Liferay), un fragment (qui doit être présent dans la page >>> source) et la remoteUrlBase (qui serait donc l'URL de mon application). >>> >>> Pour répondre à mon besoin, faut-il que je suive la même stratégie en >>> créant ma propre Extension ou existe-t-il dans ESIGate un fonctionnement >>> similaire en standard ? >>> >>> Merci d'avance pour votre aide. >>> Cordialement, >>> William >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Comprehensive Server Monitoring with Site24x7. >>> Monitor 10 servers for $9/Month. >>> Get alerted through email, SMS, voice calls or mobile push notifications. >>> Take corrective actions from your mobile device. >>> >>> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >>> _______________________________________________ >>> Webassembletool-users mailing list >>> Web...@li... >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>> >>> >> > |
|
From: William D. <wil...@gm...> - 2014-11-18 10:59:13
|
Merci pour vos retour. Finalement je suis partie sur le même fonctionnement que l'implémentation de Jahia. J'ai créé deux nouvelles classes dans ESIGate : - une nouvelle extension qui prend en paramètre une URL Liferay qui sert de template de page et un fragment qui sera remplacé par le contenu de l'application agrégée, - un nouveau renderer qui ajoute un tag "esi:include" ayant pour source l'URL Liferay et qui contient une balise "esi:replace" pour remplacer le fragment par le contenu de mon "remoteUrlBase". Cela répond parfaitement à mon besoin. Si cela vous intéresse, je peux vous envoyer le code source. William Le 15 novembre 2014 22:56, Francois-Xavier Bonnet < fra...@ce...> a écrit : > Bonjour, > > Pour intégrer une application et qu'elle soit navigable, il faut faire > dans l'autre sens : c'est l'application qui doit utiliser les pages Liferay > comme des templates en utilisant des tags <esi:include> et <esi:replace>. > Ainsi c'est l'application qui a le contrôle de la navigation. C'est > précisément l'exemple qui est décrit dans ce tutorial : > http://www.esigate.org/quickstart.html > > Dans le cas de Liferay il y a aussi une solution expérimentale qui permet > d'intégrer l'application sous forme d'une portlet : > https://github.com/Smile-SA/esigate-portlet > > Le 13 novembre 2014 14:13, William Dupuis <wil...@gm...> a > écrit : > >> Bonjour, >> Je fais appel à vous car je n'arrive pas à comprendre comment inclure une >> application dans Liferay via un serveur ESIGate dédié. >> >> Voici mon besoin : >> - Inclure sur une page Liferay une application et pouvoir naviguer dans >> cette application tout en restant dans ma page Liferay. >> >> Pour faire cela, j'ai 3 serveurs Tomcat : >> - 1 serveur ESIGate accessible via l'URL : http://test.local.env/esigate/ >> - 1 serveur Liferay accessible via l'URL : http://test.local.env/ >> - 1 serveur Tomcat avec mon appli accessible via l'URL : >> http://serveur-appli:8080/appli/ >> L'accès à mon application se fera exclusivement via ESIGate. >> >> Pour le moment, j'ai testé en ajoutant dans ma page Liferay, un tag >> esi:include : >> <esi:include src="http://serveur-appli:8080/appli/" /> >> >> L'inclusion se fait bien mais je ne peux pas naviguer dans mon >> application en restant dans ma page Liferay. >> J'ai également pas mal de problème de ré-écriture d'URL pour les fichiers >> statiques. >> Vous trouverez en pièce-jointe mon fichier esigate.properties. >> >> Pour accéder à ma page Liferay, j'utilise l'URL : >> http://test.local.env/esigate/private/liferay/mapageliferay >> >> Je pense que ma stratégie n'est pas la bonne. >> En regardant en détail comment Jahia a intégré ESIGate dans leur >> solution, j'ai vu qu'ils ont créé une nouvelle Extension afin de générer un >> tag esi:include. >> Dans les paramètres du provider, ils indiquent l'URL source (donc pour >> moi mon URL Liferay), un fragment (qui doit être présent dans la page >> source) et la remoteUrlBase (qui serait donc l'URL de mon application). >> >> Pour répondre à mon besoin, faut-il que je suive la même stratégie en >> créant ma propre Extension ou existe-t-il dans ESIGate un fonctionnement >> similaire en standard ? >> >> Merci d'avance pour votre aide. >> Cordialement, >> William >> >> >> >> ------------------------------------------------------------------------------ >> Comprehensive Server Monitoring with Site24x7. >> Monitor 10 servers for $9/Month. >> Get alerted through email, SMS, voice calls or mobile push notifications. >> Take corrective actions from your mobile device. >> >> http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> > |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-11-15 21:56:39
|
Bonjour, Pour intégrer une application et qu'elle soit navigable, il faut faire dans l'autre sens : c'est l'application qui doit utiliser les pages Liferay comme des templates en utilisant des tags <esi:include> et <esi:replace>. Ainsi c'est l'application qui a le contrôle de la navigation. C'est précisément l'exemple qui est décrit dans ce tutorial : http://www.esigate.org/quickstart.html Dans le cas de Liferay il y a aussi une solution expérimentale qui permet d'intégrer l'application sous forme d'une portlet : https://github.com/Smile-SA/esigate-portlet Le 13 novembre 2014 14:13, William Dupuis <wil...@gm...> a écrit : > Bonjour, > Je fais appel à vous car je n'arrive pas à comprendre comment inclure une > application dans Liferay via un serveur ESIGate dédié. > > Voici mon besoin : > - Inclure sur une page Liferay une application et pouvoir naviguer dans > cette application tout en restant dans ma page Liferay. > > Pour faire cela, j'ai 3 serveurs Tomcat : > - 1 serveur ESIGate accessible via l'URL : http://test.local.env/esigate/ > - 1 serveur Liferay accessible via l'URL : http://test.local.env/ > - 1 serveur Tomcat avec mon appli accessible via l'URL : > http://serveur-appli:8080/appli/ > L'accès à mon application se fera exclusivement via ESIGate. > > Pour le moment, j'ai testé en ajoutant dans ma page Liferay, un tag > esi:include : > <esi:include src="http://serveur-appli:8080/appli/" /> > > L'inclusion se fait bien mais je ne peux pas naviguer dans mon application > en restant dans ma page Liferay. > J'ai également pas mal de problème de ré-écriture d'URL pour les fichiers > statiques. > Vous trouverez en pièce-jointe mon fichier esigate.properties. > > Pour accéder à ma page Liferay, j'utilise l'URL : > http://test.local.env/esigate/private/liferay/mapageliferay > > Je pense que ma stratégie n'est pas la bonne. > En regardant en détail comment Jahia a intégré ESIGate dans leur solution, > j'ai vu qu'ils ont créé une nouvelle Extension afin de générer un tag > esi:include. > Dans les paramètres du provider, ils indiquent l'URL source (donc pour moi > mon URL Liferay), un fragment (qui doit être présent dans la page source) > et la remoteUrlBase (qui serait donc l'URL de mon application). > > Pour répondre à mon besoin, faut-il que je suive la même stratégie en > créant ma propre Extension ou existe-t-il dans ESIGate un fonctionnement > similaire en standard ? > > Merci d'avance pour votre aide. > Cordialement, > William > > > > ------------------------------------------------------------------------------ > Comprehensive Server Monitoring with Site24x7. > Monitor 10 servers for $9/Month. > Get alerted through email, SMS, voice calls or mobile push notifications. > Take corrective actions from your mobile device. > > http://pubads.g.doubleclick.net/gampad/clk?id=154624111&iu=/4140/ostg.clktrk > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: William D. <wil...@gm...> - 2014-11-13 13:13:54
|
Bonjour, Je fais appel à vous car je n'arrive pas à comprendre comment inclure une application dans Liferay via un serveur ESIGate dédié. Voici mon besoin : - Inclure sur une page Liferay une application et pouvoir naviguer dans cette application tout en restant dans ma page Liferay. Pour faire cela, j'ai 3 serveurs Tomcat : - 1 serveur ESIGate accessible via l'URL : http://test.local.env/esigate/ - 1 serveur Liferay accessible via l'URL : http://test.local.env/ - 1 serveur Tomcat avec mon appli accessible via l'URL : http://serveur-appli:8080/appli/ L'accès à mon application se fera exclusivement via ESIGate. Pour le moment, j'ai testé en ajoutant dans ma page Liferay, un tag esi:include : <esi:include src="http://serveur-appli:8080/appli/" /> L'inclusion se fait bien mais je ne peux pas naviguer dans mon application en restant dans ma page Liferay. J'ai également pas mal de problème de ré-écriture d'URL pour les fichiers statiques. Vous trouverez en pièce-jointe mon fichier esigate.properties. Pour accéder à ma page Liferay, j'utilise l'URL : http://test.local.env/esigate/private/liferay/mapageliferay Je pense que ma stratégie n'est pas la bonne. En regardant en détail comment Jahia a intégré ESIGate dans leur solution, j'ai vu qu'ils ont créé une nouvelle Extension afin de générer un tag esi:include. Dans les paramètres du provider, ils indiquent l'URL source (donc pour moi mon URL Liferay), un fragment (qui doit être présent dans la page source) et la remoteUrlBase (qui serait donc l'URL de mon application). Pour répondre à mon besoin, faut-il que je suive la même stratégie en créant ma propre Extension ou existe-t-il dans ESIGate un fonctionnement similaire en standard ? Merci d'avance pour votre aide. Cordialement, William |
|
From: Francois-Xavier B. <fra...@ce...> - 2014-11-10 11:09:08
|
Hi, In your case it is the php system that implements the logic (post, redirects...). You should let this application have the control and just use the cms as a template provider using <esi:include> and <esi:replace> tags. I think this is exactly the use case that is described in the quick start: http://www.esigate.org/quickstart.html 2014-11-10 11:47 GMT+01:00 Dave Sowerby <dav...@gm...>: > Hi, > > I'm currently trying to work out how I might be able to solve a problem > with a proof-of-concept using esigate that I've been working on. > > A have two providers: > > o A CMS which provides the theme and the page structure > o A PHP system which provides fragments based upon the user's session. > > However, I need to use posts to the PHP system in order to handle form > processing which is where my confusion arises. > > Just for clarity, here is my esigate.properties: > > origin.remoteUrlBase=http://www.cmsprovider.com > origin.mappings=/* > > php.remoteUrlBase=http://www.phpprovider.com > php.mappings=/php/* > > If I include the form through an ESI Include statement obviously > everything then works fine for the initial rendering of the form in the > resultant response. However the form target has to be a /php/ based > request so that the entities for the post are actually delivered to the > provider. > > This PHP system can only produce fragments of the page and while I could > split up the CMS page into fragments and include them that way it doesn't > feel right to be doing this. > > Have I missed some element of the esi flow that would cover this use > case? Should I be posting directly and declaring a esi:fragment of the > required result and an esi:include for the CMS page? > > Cheers, > > Dave. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > |
|
From: Philippe De O. <phi...@gm...> - 2014-11-10 11:04:04
|
Hi, You are right. You must post directly to PHP system and declare a esi:fragment for the required result. When using the esi:include, combine it with a esi:replace so you will not have to split your CMS page. BR, On Mon, Nov 10, 2014 at 11:47 AM, Dave Sowerby <dav...@gm...> wrote: > Hi, > > I'm currently trying to work out how I might be able to solve a problem > with a proof-of-concept using esigate that I've been working on. > > A have two providers: > > o A CMS which provides the theme and the page structure > o A PHP system which provides fragments based upon the user's session. > > However, I need to use posts to the PHP system in order to handle form > processing which is where my confusion arises. > > Just for clarity, here is my esigate.properties: > > origin.remoteUrlBase=http://www.cmsprovider.com > origin.mappings=/* > > php.remoteUrlBase=http://www.phpprovider.com > php.mappings=/php/* > > If I include the form through an ESI Include statement obviously > everything then works fine for the initial rendering of the form in the > resultant response. However the form target has to be a /php/ based > request so that the entities for the post are actually delivered to the > provider. > > This PHP system can only produce fragments of the page and while I could > split up the CMS page into fragments and include them that way it doesn't > feel right to be doing this. > > Have I missed some element of the esi flow that would cover this use > case? Should I be posting directly and declaring a esi:fragment of the > required result and an esi:include for the CMS page? > > Cheers, > > Dave. > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > -- Philippe De Oliveira |
|
From: Dave S. <dav...@gm...> - 2014-11-10 10:47:56
|
Hi, I'm currently trying to work out how I might be able to solve a problem with a proof-of-concept using esigate that I've been working on. A have two providers: o A CMS which provides the theme and the page structure o A PHP system which provides fragments based upon the user's session. However, I need to use posts to the PHP system in order to handle form processing which is where my confusion arises. Just for clarity, here is my esigate.properties: origin.remoteUrlBase=http://www.cmsprovider.com origin.mappings=/* php.remoteUrlBase=http://www.phpprovider.com php.mappings=/php/* If I include the form through an ESI Include statement obviously everything then works fine for the initial rendering of the form in the resultant response. However the form target has to be a /php/ based request so that the entities for the post are actually delivered to the provider. This PHP system can only produce fragments of the page and while I could split up the CMS page into fragments and include them that way it doesn't feel right to be doing this. Have I missed some element of the esi flow that would cover this use case? Should I be posting directly and declaring a esi:fragment of the required result and an esi:include for the CMS page? Cheers, Dave. |
|
From: Volker K. <vol...@gm...> - 2014-11-05 16:38:23
|
I created an issue about this: https://github.com/esigate/esigate/issues/59 thanks in advance! 2014-11-05 11:36 GMT+01:00 alexis thaveau <ale...@gm...>: > Hi, > Great ! > > Could you please create an issue on github about the ./ replacement ? > > 2014-11-04 19:16 GMT+01:00 Volker Kümmer <vol...@gm...>: > > I've seen, that you fixed that, great. Now the links are almost looking > > good. > > > > I just spottet one more problem. Wicket is always generating relative > links. > > So, when I am not on the start page the links starts with "../". These > kind > > of links are now looking very good after your commit. Thanks for that! > > > > But if I am on the start page the links start with "./". That means that > > ESIGate will generate something like this > > > > "/./wicket/resource/pathToTheResource" instead of just > > "/wicket/resource/pathToTheResource" > > > > I must say, am really impressed with the fast help and reactions here in > > this project! > > > > 2014-11-01 18:58 GMT+01:00 alexis thaveau <ale...@gm...>: > >> > >> I've created a pull request to fix that : > >> https://github.com/esigate/esigate/pull/48 > >> > >> 2014-10-31 18:43 GMT+01:00 Volker Kümmer <vol...@gm...>: > >> > thanks, for the update about the documentation. > >> > > >> > my application is now working behind esigate. But I do not like the > >> > links, > >> > that are generated. > >> > > >> > if am at the location http://localhost:8082/path/to/resource and my > >> > application is generating relative links "../../link/another/resource" > >> > then > >> > I am having this link in my html source > >> > > >> > "/path/to/resource/../../link/another/resource" > >> > > >> > is there a way to just get the link > >> > > >> > "/link/another/resource"? > >> > > >> > I tried using "esigate.fixMode=absolute", but then I am getting > totally > >> > syntactically incorrect and therefore not working links. > >> > > >> > so my question is, is there a configuration option to just get > >> > "/link/another/resource" instead of > >> > "/path/to/resource/../../link/another/resource" in the html that > esigate > >> > generates/changes? > >> > > >> > > >> > 2014-10-26 22:19 GMT+01:00 alexis thaveau <ale...@gm...>: > >> >> > >> >> Hi, > >> >> > >> >> The documentation has been updated on 5.0-SNAPSHOT version ( > >> >> http://www.esigate.org/5.0-SNAPSHOT ) > >> >> > >> >> > >> >> > >> >> 2014-10-24 16:33 GMT+02:00 Volker Kümmer <vol...@gm...>: > >> >> > just want to let you know, that with the esigate server my wicket > >> >> > application is working (just one problem, that should be possible > to > >> >> > solve). > >> >> > So it seems that the proxyservlet is doing something different, as > >> >> > with > >> >> > the > >> >> > filter my application is not working. > >> >> > > >> >> > just 2 little notes: > >> >> > - it would be helpful to correct the quickstart > >> >> > (http://www.esigate.org/quickstart.html) and add there the "s" to > the > >> >> > mapping configuration, too > >> >> > - its just cosmetic, but it would be nice, if the description line > >> >> > for > >> >> > 302 > >> >> > would be "Found", not "Temporary redirect" > >> >> > > >> >> > thanks for the help and pointers I've gotten here! > >> >> > > >> >> > 2014-10-24 14:16 GMT+02:00 Francois-Xavier Bonnet > >> >> > <fra...@ce...>: > >> >> >> > >> >> >> Can you try with "esigate.mappings" (with a "s")? > >> >> >> > >> >> >> 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" > >> >> >> <vol...@gm...> написал: > >> >> >>> > >> >> >>> >you should try esigate as a standalone proxy (esigate-server or > >> >> >>> > esigate-war). > >> >> >>> > >> >> >>> unfortunately I am not able to get esigate server working. It > seems > >> >> >>> to > >> >> >>> be > >> >> >>> any easy installation, but if I use this configuration > >> >> >>> > >> >> >>> esigate.remoteUrlBase=http://localhost:8080/ > >> >> >>> esigate.mapping=/* > >> >> >>> > >> >> >>> and this command for starting > >> >> >>> > >> >> >>> java -Desigate.config=esigate.properties -Dserver.port=8082 -jar > >> >> >>> esigate-server-5.0-SNAPSHOT.jar start > >> >> >>> > >> >> >>> I only get "No mapping defined for this url." when calling > >> >> >>> http://localhost:8082/ > >> >> >>> > >> >> >>> Am I doing something wrong? > >> >> >>> > >> >> >>> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton > >> >> >>> <nic...@gm...>: > >> >> >>>> > >> >> >>>> Hi Volker, > >> >> >>>> > >> >> >>>> The proxy filter is a new addition to esigate 5.0. > >> >> >>>> Your feedback is really valuable to catch the last bugs before > the > >> >> >>>> stable release, but if you want something that just work, you > >> >> >>>> should > >> >> >>>> try > >> >> >>>> esigate as a standalone proxy (esigate-server or esigate-war). > >> >> >>>> > >> >> >>>> We have several applications using esigate + wicket in > production > >> >> >>>> with > >> >> >>>> no issue. > >> >> >>>> > >> >> >>>> -- > >> >> >>>> Nicolas > >> >> >>>> > >> >> >>>> Le 15 oct. 2014 à 18:02, Volker Kümmer < > vol...@gm...> > >> >> >>>> a > >> >> >>>> écrit : > >> >> >>>> > >> >> >>>> hi > >> >> >>>> > >> >> >>>> good to know, that it should work in principle. > >> >> >>>> > >> >> >>>> I had not enough time, to really debug the problems, to see > where > >> >> >>>> it > >> >> >>>> originated from. > >> >> >>>> > >> >> >>>> But in the moment I am having two problems. > >> >> >>>> > >> >> >>>> 1. when the proxy filter is not in front of the wicket > >> >> >>>> application, > >> >> >>>> if I > >> >> >>>> send a redirect after a post, I get es 302 redirect. But when > the > >> >> >>>> ESIGate > >> >> >>>> proxy filter is in front of the application I will get an 307 > >> >> >>>> redirect -- I > >> >> >>>> do not know why in the moment. > >> >> >>>> > >> >> >>>> 2. when using the wicket ajax mechanisms I will always get an > >> >> >>>> error > >> >> >>>> -- > >> >> >>>> it works without any problems without the proxy filter: > >> >> >>>> > >> >> >>>> java.lang.IllegalStateException: WRITER > >> >> >>>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) > >> >> >>>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) > >> >> >>>> at org.mortbay.jetty.Server.handle(Server.java:295) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) > >> >> >>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) > >> >> >>>> at > >> >> >>>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) > >> >> >>>> at > >> >> >>>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) > >> >> >>>> at > >> >> >>>> > >> >> >>>> > >> >> >>>> > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) > >> >> >>>> > >> >> >>>> > >> >> >>>> I am not using any esi or caching functionality. I have just > >> >> >>>> configured > >> >> >>>> the proxyfilter before the application. I will see, if I can get > >> >> >>>> some > >> >> >>>> more > >> >> >>>> detailed information. > >> >> >>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet > >> >> >>>> <fra...@ce...>: > >> >> >>>>> > >> >> >>>>> Hi Volker, > >> >> >>>>> > >> >> >>>>> The beta-1 versions is currently being tested on a few > projects. > >> >> >>>>> Since > >> >> >>>>> this version, we have made a few improvements or bug fixes but > no > >> >> >>>>> blocking > >> >> >>>>> issue. > >> >> >>>>> Usually we release a new beta version every time we find a > >> >> >>>>> blocking > >> >> >>>>> issue that need a fix and the stable release comes when a major > >> >> >>>>> project > >> >> >>>>> using EsiGate is ready to go to production. > >> >> >>>>> > >> >> >>>>> I would be very interested in having more information about the > >> >> >>>>> errors > >> >> >>>>> you have. If a beta-2 is required, we could release it very > >> >> >>>>> quickly. > >> >> >>>>> > >> >> >>>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer > >> >> >>>>> <vol...@gm...>: > >> >> >>>>>> > >> >> >>>>>> Hello > >> >> >>>>>> > >> >> >>>>>> I would like to know, what the current state of ESIGate is? > >> >> >>>>>> > >> >> >>>>>> I was able (with the help of Francois-Xavier Bonnet -- > thanks!) > >> >> >>>>>> to > >> >> >>>>>> get > >> >> >>>>>> ESIGate configured, so that it served some content. > >> >> >>>>>> > >> >> >>>>>> But now I get some errors. I have ESIGate in front of a wicket > >> >> >>>>>> application and there are some problems with it. So I would > like > >> >> >>>>>> to > >> >> >>>>>> know, > >> >> >>>>>> whether there are some speciel configurations neccessary to > get > >> >> >>>>>> it > >> >> >>>>>> working > >> >> >>>>>> or if the beta-1 from february 2014 is simply outdated, > >> >> >>>>>> > >> >> >>>>>> In the moment my application runs behind ESIGate, but I have > not > >> >> >>>>>> set > >> >> >>>>>> any caching headers up to now. So I expected that the > >> >> >>>>>> application > >> >> >>>>>> would work > >> >> >>>>>> as without ESIGate. > >> >> >>>>>> > >> >> >>>>>> If it should work with the beta-1 I will further investigate > the > >> >> >>>>>> problem. But in the moment I just would like to know, if > (these) > >> >> >>>>>> problems > >> >> >>>>>> are to be expected, as it is still a beta. > >> >> >>>>>> > >> >> >>>>>> kind regards > >> >> >>>>>> Volker > >> >> >>>>>> > >> >> >>>>>> > >> >> >>>>>> > >> >> >>>>>> > >> >> >>>>>> > ------------------------------------------------------------------------------ > >> >> >>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog > Analyzer > >> >> >>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI > DSS > >> >> >>>>>> Reports > >> >> >>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White > >> >> >>>>>> paper > >> >> >>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog > >> >> >>>>>> Analyzer > >> >> >>>>>> http://p.sf.net/sfu/Zoho > >> >> >>>>>> _______________________________________________ > >> >> >>>>>> Webassembletool-users mailing list > >> >> >>>>>> Web...@li... > >> >> >>>>>> > >> >> >>>>>> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> >> >>>>>> > >> >> >>>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> > >> >> >>>> > ------------------------------------------------------------------------------ > >> >> >>>> Comprehensive Server Monitoring with Site24x7. > >> >> >>>> Monitor 10 servers for $9/Month. > >> >> >>>> Get alerted through email, SMS, voice calls or mobile push > >> >> >>>> notifications. > >> >> >>>> Take corrective actions from your mobile device. > >> >> >>>> http://p.sf.net/sfu/Zoho > >> >> >>>> > >> >> >>>> _______________________________________________ > >> >> >>>> Webassembletool-users mailing list > >> >> >>>> Web...@li... > >> >> >>>> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > >> >> >>> > ------------------------------------------------------------------------------ > >> >> >>> > >> >> >>> _______________________________________________ > >> >> >>> Webassembletool-users mailing list > >> >> >>> Web...@li... > >> >> >>> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> >> >>> > >> >> > > >> >> > > >> >> > > >> >> > > >> >> > > ------------------------------------------------------------------------------ > >> >> > > >> >> > _______________________________________________ > >> >> > Webassembletool-users mailing list > >> >> > Web...@li... > >> >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> >> > > >> > > >> > > >> > > >> > > >> > > ------------------------------------------------------------------------------ > >> > > >> > _______________________________________________ > >> > Webassembletool-users mailing list > >> > Web...@li... > >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> > > > > > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Webassembletool-users mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > |
|
From: alexis t. <ale...@gm...> - 2014-11-05 10:37:15
|
Hi, Great ! Could you please create an issue on github about the ./ replacement ? 2014-11-04 19:16 GMT+01:00 Volker Kümmer <vol...@gm...>: > I've seen, that you fixed that, great. Now the links are almost looking > good. > > I just spottet one more problem. Wicket is always generating relative links. > So, when I am not on the start page the links starts with "../". These kind > of links are now looking very good after your commit. Thanks for that! > > But if I am on the start page the links start with "./". That means that > ESIGate will generate something like this > > "/./wicket/resource/pathToTheResource" instead of just > "/wicket/resource/pathToTheResource" > > I must say, am really impressed with the fast help and reactions here in > this project! > > 2014-11-01 18:58 GMT+01:00 alexis thaveau <ale...@gm...>: >> >> I've created a pull request to fix that : >> https://github.com/esigate/esigate/pull/48 >> >> 2014-10-31 18:43 GMT+01:00 Volker Kümmer <vol...@gm...>: >> > thanks, for the update about the documentation. >> > >> > my application is now working behind esigate. But I do not like the >> > links, >> > that are generated. >> > >> > if am at the location http://localhost:8082/path/to/resource and my >> > application is generating relative links "../../link/another/resource" >> > then >> > I am having this link in my html source >> > >> > "/path/to/resource/../../link/another/resource" >> > >> > is there a way to just get the link >> > >> > "/link/another/resource"? >> > >> > I tried using "esigate.fixMode=absolute", but then I am getting totally >> > syntactically incorrect and therefore not working links. >> > >> > so my question is, is there a configuration option to just get >> > "/link/another/resource" instead of >> > "/path/to/resource/../../link/another/resource" in the html that esigate >> > generates/changes? >> > >> > >> > 2014-10-26 22:19 GMT+01:00 alexis thaveau <ale...@gm...>: >> >> >> >> Hi, >> >> >> >> The documentation has been updated on 5.0-SNAPSHOT version ( >> >> http://www.esigate.org/5.0-SNAPSHOT ) >> >> >> >> >> >> >> >> 2014-10-24 16:33 GMT+02:00 Volker Kümmer <vol...@gm...>: >> >> > just want to let you know, that with the esigate server my wicket >> >> > application is working (just one problem, that should be possible to >> >> > solve). >> >> > So it seems that the proxyservlet is doing something different, as >> >> > with >> >> > the >> >> > filter my application is not working. >> >> > >> >> > just 2 little notes: >> >> > - it would be helpful to correct the quickstart >> >> > (http://www.esigate.org/quickstart.html) and add there the "s" to the >> >> > mapping configuration, too >> >> > - its just cosmetic, but it would be nice, if the description line >> >> > for >> >> > 302 >> >> > would be "Found", not "Temporary redirect" >> >> > >> >> > thanks for the help and pointers I've gotten here! >> >> > >> >> > 2014-10-24 14:16 GMT+02:00 Francois-Xavier Bonnet >> >> > <fra...@ce...>: >> >> >> >> >> >> Can you try with "esigate.mappings" (with a "s")? >> >> >> >> >> >> 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" >> >> >> <vol...@gm...> написал: >> >> >>> >> >> >>> >you should try esigate as a standalone proxy (esigate-server or >> >> >>> > esigate-war). >> >> >>> >> >> >>> unfortunately I am not able to get esigate server working. It seems >> >> >>> to >> >> >>> be >> >> >>> any easy installation, but if I use this configuration >> >> >>> >> >> >>> esigate.remoteUrlBase=http://localhost:8080/ >> >> >>> esigate.mapping=/* >> >> >>> >> >> >>> and this command for starting >> >> >>> >> >> >>> java -Desigate.config=esigate.properties -Dserver.port=8082 -jar >> >> >>> esigate-server-5.0-SNAPSHOT.jar start >> >> >>> >> >> >>> I only get "No mapping defined for this url." when calling >> >> >>> http://localhost:8082/ >> >> >>> >> >> >>> Am I doing something wrong? >> >> >>> >> >> >>> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton >> >> >>> <nic...@gm...>: >> >> >>>> >> >> >>>> Hi Volker, >> >> >>>> >> >> >>>> The proxy filter is a new addition to esigate 5.0. >> >> >>>> Your feedback is really valuable to catch the last bugs before the >> >> >>>> stable release, but if you want something that just work, you >> >> >>>> should >> >> >>>> try >> >> >>>> esigate as a standalone proxy (esigate-server or esigate-war). >> >> >>>> >> >> >>>> We have several applications using esigate + wicket in production >> >> >>>> with >> >> >>>> no issue. >> >> >>>> >> >> >>>> -- >> >> >>>> Nicolas >> >> >>>> >> >> >>>> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> >> >> >>>> a >> >> >>>> écrit : >> >> >>>> >> >> >>>> hi >> >> >>>> >> >> >>>> good to know, that it should work in principle. >> >> >>>> >> >> >>>> I had not enough time, to really debug the problems, to see where >> >> >>>> it >> >> >>>> originated from. >> >> >>>> >> >> >>>> But in the moment I am having two problems. >> >> >>>> >> >> >>>> 1. when the proxy filter is not in front of the wicket >> >> >>>> application, >> >> >>>> if I >> >> >>>> send a redirect after a post, I get es 302 redirect. But when the >> >> >>>> ESIGate >> >> >>>> proxy filter is in front of the application I will get an 307 >> >> >>>> redirect -- I >> >> >>>> do not know why in the moment. >> >> >>>> >> >> >>>> 2. when using the wicket ajax mechanisms I will always get an >> >> >>>> error >> >> >>>> -- >> >> >>>> it works without any problems without the proxy filter: >> >> >>>> >> >> >>>> java.lang.IllegalStateException: WRITER >> >> >>>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) >> >> >>>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >> >> >>>> at >> >> >>>> >> >> >>>> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >> >> >>>> at org.mortbay.jetty.Server.handle(Server.java:295) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) >> >> >>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) >> >> >>>> at >> >> >>>> org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) >> >> >>>> at >> >> >>>> org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) >> >> >>>> at >> >> >>>> >> >> >>>> >> >> >>>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >> >> >>>> >> >> >>>> >> >> >>>> I am not using any esi or caching functionality. I have just >> >> >>>> configured >> >> >>>> the proxyfilter before the application. I will see, if I can get >> >> >>>> some >> >> >>>> more >> >> >>>> detailed information. >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet >> >> >>>> <fra...@ce...>: >> >> >>>>> >> >> >>>>> Hi Volker, >> >> >>>>> >> >> >>>>> The beta-1 versions is currently being tested on a few projects. >> >> >>>>> Since >> >> >>>>> this version, we have made a few improvements or bug fixes but no >> >> >>>>> blocking >> >> >>>>> issue. >> >> >>>>> Usually we release a new beta version every time we find a >> >> >>>>> blocking >> >> >>>>> issue that need a fix and the stable release comes when a major >> >> >>>>> project >> >> >>>>> using EsiGate is ready to go to production. >> >> >>>>> >> >> >>>>> I would be very interested in having more information about the >> >> >>>>> errors >> >> >>>>> you have. If a beta-2 is required, we could release it very >> >> >>>>> quickly. >> >> >>>>> >> >> >>>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer >> >> >>>>> <vol...@gm...>: >> >> >>>>>> >> >> >>>>>> Hello >> >> >>>>>> >> >> >>>>>> I would like to know, what the current state of ESIGate is? >> >> >>>>>> >> >> >>>>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) >> >> >>>>>> to >> >> >>>>>> get >> >> >>>>>> ESIGate configured, so that it served some content. >> >> >>>>>> >> >> >>>>>> But now I get some errors. I have ESIGate in front of a wicket >> >> >>>>>> application and there are some problems with it. So I would like >> >> >>>>>> to >> >> >>>>>> know, >> >> >>>>>> whether there are some speciel configurations neccessary to get >> >> >>>>>> it >> >> >>>>>> working >> >> >>>>>> or if the beta-1 from february 2014 is simply outdated, >> >> >>>>>> >> >> >>>>>> In the moment my application runs behind ESIGate, but I have not >> >> >>>>>> set >> >> >>>>>> any caching headers up to now. So I expected that the >> >> >>>>>> application >> >> >>>>>> would work >> >> >>>>>> as without ESIGate. >> >> >>>>>> >> >> >>>>>> If it should work with the beta-1 I will further investigate the >> >> >>>>>> problem. But in the moment I just would like to know, if (these) >> >> >>>>>> problems >> >> >>>>>> are to be expected, as it is still a beta. >> >> >>>>>> >> >> >>>>>> kind regards >> >> >>>>>> Volker >> >> >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> >>>>>> >> >> >>>>>> ------------------------------------------------------------------------------ >> >> >>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> >> >>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >> >> >>>>>> Reports >> >> >>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White >> >> >>>>>> paper >> >> >>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog >> >> >>>>>> Analyzer >> >> >>>>>> http://p.sf.net/sfu/Zoho >> >> >>>>>> _______________________________________________ >> >> >>>>>> Webassembletool-users mailing list >> >> >>>>>> Web...@li... >> >> >>>>>> >> >> >>>>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> >>>>>> >> >> >>>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> >> >> >>>> ------------------------------------------------------------------------------ >> >> >>>> Comprehensive Server Monitoring with Site24x7. >> >> >>>> Monitor 10 servers for $9/Month. >> >> >>>> Get alerted through email, SMS, voice calls or mobile push >> >> >>>> notifications. >> >> >>>> Take corrective actions from your mobile device. >> >> >>>> http://p.sf.net/sfu/Zoho >> >> >>>> >> >> >>>> _______________________________________________ >> >> >>>> Webassembletool-users mailing list >> >> >>>> Web...@li... >> >> >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> >> >> >>> ------------------------------------------------------------------------------ >> >> >>> >> >> >>> _______________________________________________ >> >> >>> Webassembletool-users mailing list >> >> >>> Web...@li... >> >> >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> >>> >> >> > >> >> > >> >> > >> >> > >> >> > ------------------------------------------------------------------------------ >> >> > >> >> > _______________________________________________ >> >> > Webassembletool-users mailing list >> >> > Web...@li... >> >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> > >> > >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Webassembletool-users mailing list >> > Web...@li... >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > |
|
From: Volker K. <vol...@gm...> - 2014-11-04 18:16:35
|
I've seen, that you fixed that, great. Now the links are almost looking good. I just spottet one more problem. Wicket is always generating relative links. So, when I am not on the start page the links starts with "../". These kind of links are now looking very good after your commit. Thanks for that! But if I am on the start page the links start with "./". That means that ESIGate will generate something like this "/./wicket/resource/pathToTheResource" instead of just "/wicket/resource/pathToTheResource" I must say, am really impressed with the fast help and reactions here in this project! 2014-11-01 18:58 GMT+01:00 alexis thaveau <ale...@gm...>: > I've created a pull request to fix that : > https://github.com/esigate/esigate/pull/48 > > 2014-10-31 18:43 GMT+01:00 Volker Kümmer <vol...@gm...>: > > thanks, for the update about the documentation. > > > > my application is now working behind esigate. But I do not like the > links, > > that are generated. > > > > if am at the location http://localhost:8082/path/to/resource and my > > application is generating relative links "../../link/another/resource" > then > > I am having this link in my html source > > > > "/path/to/resource/../../link/another/resource" > > > > is there a way to just get the link > > > > "/link/another/resource"? > > > > I tried using "esigate.fixMode=absolute", but then I am getting totally > > syntactically incorrect and therefore not working links. > > > > so my question is, is there a configuration option to just get > > "/link/another/resource" instead of > > "/path/to/resource/../../link/another/resource" in the html that esigate > > generates/changes? > > > > > > 2014-10-26 22:19 GMT+01:00 alexis thaveau <ale...@gm...>: > >> > >> Hi, > >> > >> The documentation has been updated on 5.0-SNAPSHOT version ( > >> http://www.esigate.org/5.0-SNAPSHOT ) > >> > >> > >> > >> 2014-10-24 16:33 GMT+02:00 Volker Kümmer <vol...@gm...>: > >> > just want to let you know, that with the esigate server my wicket > >> > application is working (just one problem, that should be possible to > >> > solve). > >> > So it seems that the proxyservlet is doing something different, as > with > >> > the > >> > filter my application is not working. > >> > > >> > just 2 little notes: > >> > - it would be helpful to correct the quickstart > >> > (http://www.esigate.org/quickstart.html) and add there the "s" to the > >> > mapping configuration, too > >> > - its just cosmetic, but it would be nice, if the description line for > >> > 302 > >> > would be "Found", not "Temporary redirect" > >> > > >> > thanks for the help and pointers I've gotten here! > >> > > >> > 2014-10-24 14:16 GMT+02:00 Francois-Xavier Bonnet > >> > <fra...@ce...>: > >> >> > >> >> Can you try with "esigate.mappings" (with a "s")? > >> >> > >> >> 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" > >> >> <vol...@gm...> написал: > >> >>> > >> >>> >you should try esigate as a standalone proxy (esigate-server or > >> >>> > esigate-war). > >> >>> > >> >>> unfortunately I am not able to get esigate server working. It seems > to > >> >>> be > >> >>> any easy installation, but if I use this configuration > >> >>> > >> >>> esigate.remoteUrlBase=http://localhost:8080/ > >> >>> esigate.mapping=/* > >> >>> > >> >>> and this command for starting > >> >>> > >> >>> java -Desigate.config=esigate.properties -Dserver.port=8082 -jar > >> >>> esigate-server-5.0-SNAPSHOT.jar start > >> >>> > >> >>> I only get "No mapping defined for this url." when calling > >> >>> http://localhost:8082/ > >> >>> > >> >>> Am I doing something wrong? > >> >>> > >> >>> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton > >> >>> <nic...@gm...>: > >> >>>> > >> >>>> Hi Volker, > >> >>>> > >> >>>> The proxy filter is a new addition to esigate 5.0. > >> >>>> Your feedback is really valuable to catch the last bugs before the > >> >>>> stable release, but if you want something that just work, you > should > >> >>>> try > >> >>>> esigate as a standalone proxy (esigate-server or esigate-war). > >> >>>> > >> >>>> We have several applications using esigate + wicket in production > >> >>>> with > >> >>>> no issue. > >> >>>> > >> >>>> -- > >> >>>> Nicolas > >> >>>> > >> >>>> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> > a > >> >>>> écrit : > >> >>>> > >> >>>> hi > >> >>>> > >> >>>> good to know, that it should work in principle. > >> >>>> > >> >>>> I had not enough time, to really debug the problems, to see where > it > >> >>>> originated from. > >> >>>> > >> >>>> But in the moment I am having two problems. > >> >>>> > >> >>>> 1. when the proxy filter is not in front of the wicket application, > >> >>>> if I > >> >>>> send a redirect after a post, I get es 302 redirect. But when the > >> >>>> ESIGate > >> >>>> proxy filter is in front of the application I will get an 307 > >> >>>> redirect -- I > >> >>>> do not know why in the moment. > >> >>>> > >> >>>> 2. when using the wicket ajax mechanisms I will always get an error > >> >>>> -- > >> >>>> it works without any problems without the proxy filter: > >> >>>> > >> >>>> java.lang.IllegalStateException: WRITER > >> >>>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) > >> >>>> at > >> >>>> > >> >>>> > org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) > >> >>>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) > >> >>>> at > >> >>>> > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) > >> >>>> at org.mortbay.jetty.Server.handle(Server.java:295) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) > >> >>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) > >> >>>> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) > >> >>>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) > >> >>>> at > >> >>>> > >> >>>> > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) > >> >>>> > >> >>>> > >> >>>> I am not using any esi or caching functionality. I have just > >> >>>> configured > >> >>>> the proxyfilter before the application. I will see, if I can get > some > >> >>>> more > >> >>>> detailed information. > >> >>>> > >> >>>> > >> >>>> > >> >>>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet > >> >>>> <fra...@ce...>: > >> >>>>> > >> >>>>> Hi Volker, > >> >>>>> > >> >>>>> The beta-1 versions is currently being tested on a few projects. > >> >>>>> Since > >> >>>>> this version, we have made a few improvements or bug fixes but no > >> >>>>> blocking > >> >>>>> issue. > >> >>>>> Usually we release a new beta version every time we find a > blocking > >> >>>>> issue that need a fix and the stable release comes when a major > >> >>>>> project > >> >>>>> using EsiGate is ready to go to production. > >> >>>>> > >> >>>>> I would be very interested in having more information about the > >> >>>>> errors > >> >>>>> you have. If a beta-2 is required, we could release it very > quickly. > >> >>>>> > >> >>>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer < > vol...@gm...>: > >> >>>>>> > >> >>>>>> Hello > >> >>>>>> > >> >>>>>> I would like to know, what the current state of ESIGate is? > >> >>>>>> > >> >>>>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) > to > >> >>>>>> get > >> >>>>>> ESIGate configured, so that it served some content. > >> >>>>>> > >> >>>>>> But now I get some errors. I have ESIGate in front of a wicket > >> >>>>>> application and there are some problems with it. So I would like > to > >> >>>>>> know, > >> >>>>>> whether there are some speciel configurations neccessary to get > it > >> >>>>>> working > >> >>>>>> or if the beta-1 from february 2014 is simply outdated, > >> >>>>>> > >> >>>>>> In the moment my application runs behind ESIGate, but I have not > >> >>>>>> set > >> >>>>>> any caching headers up to now. So I expected that the application > >> >>>>>> would work > >> >>>>>> as without ESIGate. > >> >>>>>> > >> >>>>>> If it should work with the beta-1 I will further investigate the > >> >>>>>> problem. But in the moment I just would like to know, if (these) > >> >>>>>> problems > >> >>>>>> are to be expected, as it is still a beta. > >> >>>>>> > >> >>>>>> kind regards > >> >>>>>> Volker > >> >>>>>> > >> >>>>>> > >> >>>>>> > >> >>>>>> > ------------------------------------------------------------------------------ > >> >>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > >> >>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS > >> >>>>>> Reports > >> >>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White > >> >>>>>> paper > >> >>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog > >> >>>>>> Analyzer > >> >>>>>> http://p.sf.net/sfu/Zoho > >> >>>>>> _______________________________________________ > >> >>>>>> Webassembletool-users mailing list > >> >>>>>> Web...@li... > >> >>>>>> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> >>>>>> > >> >>>>> > >> >>>> > >> >>>> > >> >>>> > >> >>>> > ------------------------------------------------------------------------------ > >> >>>> Comprehensive Server Monitoring with Site24x7. > >> >>>> Monitor 10 servers for $9/Month. > >> >>>> Get alerted through email, SMS, voice calls or mobile push > >> >>>> notifications. > >> >>>> Take corrective actions from your mobile device. > >> >>>> http://p.sf.net/sfu/Zoho > >> >>>> > >> >>>> _______________________________________________ > >> >>>> Webassembletool-users mailing list > >> >>>> Web...@li... > >> >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > >> >>> > ------------------------------------------------------------------------------ > >> >>> > >> >>> _______________________________________________ > >> >>> Webassembletool-users mailing list > >> >>> Web...@li... > >> >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> >>> > >> > > >> > > >> > > >> > > ------------------------------------------------------------------------------ > >> > > >> > _______________________________________________ > >> > Webassembletool-users mailing list > >> > Web...@li... > >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >> > > > > > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Webassembletool-users mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > |
|
From: alexis t. <ale...@gm...> - 2014-11-03 16:47:18
|
Bonjour Ahmed, Il me faut plus de détail pour pouvoir t'aider. Peux tu me donner les URL d'origine des CSS/JS tel qu'ils sont dans ton application et le résultat de la réecriture coté Liferay. Peux tu également me fournir le fichier de log Liferay avec la category log4j fr.smile.liferay en DEBUG ? Sur quelle version de liferay as tu déployé esigate ? a+, Alexis Le 3 novembre 2014 17:35, Romain <as...@gm...> a écrit : > Bonjour, > N'étant pas le développeur ni le mainteneur de ce projet, je ne peut vous aider directement. > Cependant, quelqu'un dans la liste pourra peut être vous aider, pensez donc à les conserver en copie du mail =) > > Suite à la manipulation d'Alexis, le projet esigate-portlet est officiellement disponible dans l'organisation Smile-SA : > - https://github.com/Smile-SA/esigate-portlet > > Cordialement. > __ > Romain > > > > > Le 3 nov. 2014 à 17:20, Ahmed Drira <ahm...@gm...> a écrit : > >> Bonjour >> le portlet présente quelque anomalie lors de la réécriture des url >> pour mon cas aucun fichier css , png ni js n'est importer pour mon application héberger sur http://x.IP public...x:8080/smart..t >> est ce que c'est configurer pour un cas particulier , le site esigate par exemple ?? >> puis je avoir du support , on souhaite utuliser esigate pour intégrer plusieur application dans un portail liferay . >> >> Le 23 octobre 2014 10:30, Romain <as...@gm...> a écrit : >> Yop, >> >> Alexis avait travaillé sur ce sujet il y a peu. >> Quelques traces sur le net : >> >> - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-1-2 >> - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-2-2 >> >> Je ne sais pas s'il est prévu que Smile ouvre ses sources ou non ... >> >> Si ce projet passe en opensource, il serait d'ailleurs peut être bon d'en parler sur ce post de forum : >> - https://www.liferay.com/community/forums/-/message_boards/message/40195522 >> (l'ancien projet sur google code n'est plus d'actualité). >> >> __ >> Romain >> >> >> >> >> Le 23 oct. 2014 à 11:19, Philippe De Oliveira <phi...@gm...> a écrit : >> >> > Bonjour, >> > >> > Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins d'un an et ça fonctionne. >> > >> > Cordialement, >> > >> > 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: >> > Bonjour >> > est ce que possible de faire appel à esigate + esi:include pour intégrer une application tiers dans ma portail à travers une portlet >> > bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et ajouter esigate-core et esigate-servlet avec mes jar >> > >> > Bien cordialement >> > -- >> > Ahmed DRIRA >> > Computer engineer >> > S.A.R.L. Alpha Engineering - Tunisia >> > Résidence El Habib, Bloc 3 - Bureaux 33 & 34 >> > 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis >> > | URL : www.alpha-engineering.net >> > | Mob : 55 61 47 88 >> > | Te : 71 96 49 06 >> > | Fax : 71 96 41 53 >> > >> > ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Webassembletool-users mailing list >> > Web...@li... >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> > >> > >> > >> > >> > -- >> > Philippe De Oliveira >> > >> > ------------------------------------------------------------------------------ >> > _______________________________________________ >> > Webassembletool-users mailing list >> > Web...@li... >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >> >> >> >> -- >> Ahmed DRIRA >> Computer engineer >> S.A.R.L. Alpha Engineering - Tunisia >> Résidence El Habib, Bloc 3 - Bureaux 33 & 34 >> 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis >> | URL : www.alpha-engineering.net >> | Mob : 55 61 47 88 >> | Te : 71 96 49 06 >> | Fax : 71 96 41 53 > > > ------------------------------------------------------------------------------ > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users |
|
From: Ahmed D. <ahm...@gm...> - 2014-11-03 16:42:27
|
Bonjour le portlet présente quelque anomalie lors de la réécriture des url pour mon cas aucun fichier css , png ni js n'est importer pour mon application héberger sur http://x.IP public...x:8080/smart..t est ce que c'est configurer pour un cas particulier , le site esigate par exemple ?? puis je avoir du support , on souhaite utuliser esigate pour intégrer plusieur application dans un portail liferay . Le 23 octobre 2014 10:30, Romain <as...@gm...> a écrit : Yop, > > Alexis avait travaillé sur ce sujet il y a peu. > Quelques traces sur le net : > > - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-1-2 > - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-2-2 > > Je ne sais pas s'il est prévu que Smile ouvre ses sources ou non ... > > Si ce projet passe en opensource, il serait d'ailleurs peut être bon d'en > parler sur ce post de forum : > - > https://www.liferay.com/community/forums/-/message_boards/message/40195522 > (l'ancien projet sur google code n'est plus d'actualité). > > __ > Romain > > > > > Le 23 oct. 2014 à 11:19, Philippe De Oliveira < > phi...@gm...> a écrit : > > > Bonjour, > > > > Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins > d'un an et ça fonctionne. > > > > Cordialement, > > > > 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: > > Bonjour > > est ce que possible de faire appel à esigate + esi:include pour intégrer > une application tiers dans ma portail à travers une portlet > > bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet > et ajouter esigate-core et esigate-servlet avec mes jar > > > > Bien cordialement > > -- > > Ahmed DRIRA > > Computer engineer > > S.A.R.L. Alpha Engineering - Tunisia > > Résidence El Habib, Bloc 3 - Bureaux 33 & 34 > > 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis > > | URL : www.alpha-engineering.net > > | Mob : 55 61 47 88 > > | Te : 71 96 49 06 > > | Fax : 71 96 41 53 > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Webassembletool-users mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > > > > > > > -- > > Philippe De Oliveira > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Webassembletool-users mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > -- Ahmed DRIRA Computer engineer S.A.R.L. Alpha Engineering - Tunisia Résidence El Habib, Bloc 3 - Bureaux 33 & 34 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis | URL : www.alpha-engineering.net | Mob : 55 61 47 88 | Te : 71 96 49 06 | Fax : 71 96 41 53 -- Ahmed DRIRA Computer engineer S.A.R.L. Alpha Engineering - Tunisia Résidence El Habib, Bloc 3 - Bureaux 33 & 34 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis | URL : www.alpha-engineering.net | Mob : 55 61 47 88 | Te : 71 96 49 06 | Fax : 71 96 41 53 |
|
From: Romain <as...@gm...> - 2014-11-03 16:35:09
|
Bonjour, N'étant pas le développeur ni le mainteneur de ce projet, je ne peut vous aider directement. Cependant, quelqu'un dans la liste pourra peut être vous aider, pensez donc à les conserver en copie du mail =) Suite à la manipulation d'Alexis, le projet esigate-portlet est officiellement disponible dans l'organisation Smile-SA : - https://github.com/Smile-SA/esigate-portlet Cordialement. __ Romain Le 3 nov. 2014 à 17:20, Ahmed Drira <ahm...@gm...> a écrit : > Bonjour > le portlet présente quelque anomalie lors de la réécriture des url > pour mon cas aucun fichier css , png ni js n'est importer pour mon application héberger sur http://x.IP public...x:8080/smart..t > est ce que c'est configurer pour un cas particulier , le site esigate par exemple ?? > puis je avoir du support , on souhaite utuliser esigate pour intégrer plusieur application dans un portail liferay . > > Le 23 octobre 2014 10:30, Romain <as...@gm...> a écrit : > Yop, > > Alexis avait travaillé sur ce sujet il y a peu. > Quelques traces sur le net : > > - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-1-2 > - http://blog.smile.fr/Integrer-metier-et-liferay-avec-esi-gate-partie-2-2 > > Je ne sais pas s'il est prévu que Smile ouvre ses sources ou non ... > > Si ce projet passe en opensource, il serait d'ailleurs peut être bon d'en parler sur ce post de forum : > - https://www.liferay.com/community/forums/-/message_boards/message/40195522 > (l'ancien projet sur google code n'est plus d'actualité). > > __ > Romain > > > > > Le 23 oct. 2014 à 11:19, Philippe De Oliveira <phi...@gm...> a écrit : > > > Bonjour, > > > > Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins d'un an et ça fonctionne. > > > > Cordialement, > > > > 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: > > Bonjour > > est ce que possible de faire appel à esigate + esi:include pour intégrer une application tiers dans ma portail à travers une portlet > > bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et ajouter esigate-core et esigate-servlet avec mes jar > > > > Bien cordialement > > -- > > Ahmed DRIRA > > Computer engineer > > S.A.R.L. Alpha Engineering - Tunisia > > Résidence El Habib, Bloc 3 - Bureaux 33 & 34 > > 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis > > | URL : www.alpha-engineering.net > > | Mob : 55 61 47 88 > > | Te : 71 96 49 06 > > | Fax : 71 96 41 53 > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Webassembletool-users mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > > > > > > > -- > > Philippe De Oliveira > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > > Webassembletool-users mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > > > -- > Ahmed DRIRA > Computer engineer > S.A.R.L. Alpha Engineering - Tunisia > Résidence El Habib, Bloc 3 - Bureaux 33 & 34 > 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis > | URL : www.alpha-engineering.net > | Mob : 55 61 47 88 > | Te : 71 96 49 06 > | Fax : 71 96 41 53 |
|
From: alexis t. <ale...@gm...> - 2014-11-01 17:58:47
|
I've created a pull request to fix that : https://github.com/esigate/esigate/pull/48 2014-10-31 18:43 GMT+01:00 Volker Kümmer <vol...@gm...>: > thanks, for the update about the documentation. > > my application is now working behind esigate. But I do not like the links, > that are generated. > > if am at the location http://localhost:8082/path/to/resource and my > application is generating relative links "../../link/another/resource" then > I am having this link in my html source > > "/path/to/resource/../../link/another/resource" > > is there a way to just get the link > > "/link/another/resource"? > > I tried using "esigate.fixMode=absolute", but then I am getting totally > syntactically incorrect and therefore not working links. > > so my question is, is there a configuration option to just get > "/link/another/resource" instead of > "/path/to/resource/../../link/another/resource" in the html that esigate > generates/changes? > > > 2014-10-26 22:19 GMT+01:00 alexis thaveau <ale...@gm...>: >> >> Hi, >> >> The documentation has been updated on 5.0-SNAPSHOT version ( >> http://www.esigate.org/5.0-SNAPSHOT ) >> >> >> >> 2014-10-24 16:33 GMT+02:00 Volker Kümmer <vol...@gm...>: >> > just want to let you know, that with the esigate server my wicket >> > application is working (just one problem, that should be possible to >> > solve). >> > So it seems that the proxyservlet is doing something different, as with >> > the >> > filter my application is not working. >> > >> > just 2 little notes: >> > - it would be helpful to correct the quickstart >> > (http://www.esigate.org/quickstart.html) and add there the "s" to the >> > mapping configuration, too >> > - its just cosmetic, but it would be nice, if the description line for >> > 302 >> > would be "Found", not "Temporary redirect" >> > >> > thanks for the help and pointers I've gotten here! >> > >> > 2014-10-24 14:16 GMT+02:00 Francois-Xavier Bonnet >> > <fra...@ce...>: >> >> >> >> Can you try with "esigate.mappings" (with a "s")? >> >> >> >> 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" >> >> <vol...@gm...> написал: >> >>> >> >>> >you should try esigate as a standalone proxy (esigate-server or >> >>> > esigate-war). >> >>> >> >>> unfortunately I am not able to get esigate server working. It seems to >> >>> be >> >>> any easy installation, but if I use this configuration >> >>> >> >>> esigate.remoteUrlBase=http://localhost:8080/ >> >>> esigate.mapping=/* >> >>> >> >>> and this command for starting >> >>> >> >>> java -Desigate.config=esigate.properties -Dserver.port=8082 -jar >> >>> esigate-server-5.0-SNAPSHOT.jar start >> >>> >> >>> I only get "No mapping defined for this url." when calling >> >>> http://localhost:8082/ >> >>> >> >>> Am I doing something wrong? >> >>> >> >>> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton >> >>> <nic...@gm...>: >> >>>> >> >>>> Hi Volker, >> >>>> >> >>>> The proxy filter is a new addition to esigate 5.0. >> >>>> Your feedback is really valuable to catch the last bugs before the >> >>>> stable release, but if you want something that just work, you should >> >>>> try >> >>>> esigate as a standalone proxy (esigate-server or esigate-war). >> >>>> >> >>>> We have several applications using esigate + wicket in production >> >>>> with >> >>>> no issue. >> >>>> >> >>>> -- >> >>>> Nicolas >> >>>> >> >>>> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a >> >>>> écrit : >> >>>> >> >>>> hi >> >>>> >> >>>> good to know, that it should work in principle. >> >>>> >> >>>> I had not enough time, to really debug the problems, to see where it >> >>>> originated from. >> >>>> >> >>>> But in the moment I am having two problems. >> >>>> >> >>>> 1. when the proxy filter is not in front of the wicket application, >> >>>> if I >> >>>> send a redirect after a post, I get es 302 redirect. But when the >> >>>> ESIGate >> >>>> proxy filter is in front of the application I will get an 307 >> >>>> redirect -- I >> >>>> do not know why in the moment. >> >>>> >> >>>> 2. when using the wicket ajax mechanisms I will always get an error >> >>>> -- >> >>>> it works without any problems without the proxy filter: >> >>>> >> >>>> java.lang.IllegalStateException: WRITER >> >>>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) >> >>>> at >> >>>> >> >>>> org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) >> >>>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) >> >>>> at >> >>>> org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) >> >>>> at org.mortbay.jetty.Server.handle(Server.java:295) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) >> >>>> at >> >>>> >> >>>> org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) >> >>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) >> >>>> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) >> >>>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) >> >>>> at >> >>>> >> >>>> org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) >> >>>> at >> >>>> >> >>>> org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) >> >>>> >> >>>> >> >>>> I am not using any esi or caching functionality. I have just >> >>>> configured >> >>>> the proxyfilter before the application. I will see, if I can get some >> >>>> more >> >>>> detailed information. >> >>>> >> >>>> >> >>>> >> >>>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet >> >>>> <fra...@ce...>: >> >>>>> >> >>>>> Hi Volker, >> >>>>> >> >>>>> The beta-1 versions is currently being tested on a few projects. >> >>>>> Since >> >>>>> this version, we have made a few improvements or bug fixes but no >> >>>>> blocking >> >>>>> issue. >> >>>>> Usually we release a new beta version every time we find a blocking >> >>>>> issue that need a fix and the stable release comes when a major >> >>>>> project >> >>>>> using EsiGate is ready to go to production. >> >>>>> >> >>>>> I would be very interested in having more information about the >> >>>>> errors >> >>>>> you have. If a beta-2 is required, we could release it very quickly. >> >>>>> >> >>>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: >> >>>>>> >> >>>>>> Hello >> >>>>>> >> >>>>>> I would like to know, what the current state of ESIGate is? >> >>>>>> >> >>>>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to >> >>>>>> get >> >>>>>> ESIGate configured, so that it served some content. >> >>>>>> >> >>>>>> But now I get some errors. I have ESIGate in front of a wicket >> >>>>>> application and there are some problems with it. So I would like to >> >>>>>> know, >> >>>>>> whether there are some speciel configurations neccessary to get it >> >>>>>> working >> >>>>>> or if the beta-1 from february 2014 is simply outdated, >> >>>>>> >> >>>>>> In the moment my application runs behind ESIGate, but I have not >> >>>>>> set >> >>>>>> any caching headers up to now. So I expected that the application >> >>>>>> would work >> >>>>>> as without ESIGate. >> >>>>>> >> >>>>>> If it should work with the beta-1 I will further investigate the >> >>>>>> problem. But in the moment I just would like to know, if (these) >> >>>>>> problems >> >>>>>> are to be expected, as it is still a beta. >> >>>>>> >> >>>>>> kind regards >> >>>>>> Volker >> >>>>>> >> >>>>>> >> >>>>>> >> >>>>>> ------------------------------------------------------------------------------ >> >>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer >> >>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS >> >>>>>> Reports >> >>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White >> >>>>>> paper >> >>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog >> >>>>>> Analyzer >> >>>>>> http://p.sf.net/sfu/Zoho >> >>>>>> _______________________________________________ >> >>>>>> Webassembletool-users mailing list >> >>>>>> Web...@li... >> >>>>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >>>>>> >> >>>>> >> >>>> >> >>>> >> >>>> >> >>>> ------------------------------------------------------------------------------ >> >>>> Comprehensive Server Monitoring with Site24x7. >> >>>> Monitor 10 servers for $9/Month. >> >>>> Get alerted through email, SMS, voice calls or mobile push >> >>>> notifications. >> >>>> Take corrective actions from your mobile device. >> >>>> http://p.sf.net/sfu/Zoho >> >>>> >> >>>> _______________________________________________ >> >>>> Webassembletool-users mailing list >> >>>> Web...@li... >> >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >>> >> >>> >> >>> >> >>> >> >>> >> >>> ------------------------------------------------------------------------------ >> >>> >> >>> _______________________________________________ >> >>> Webassembletool-users mailing list >> >>> Web...@li... >> >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> >>> >> > >> > >> > >> > ------------------------------------------------------------------------------ >> > >> > _______________________________________________ >> > Webassembletool-users mailing list >> > Web...@li... >> > https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> > > > > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > |
|
From: Volker K. <vol...@gm...> - 2014-10-31 17:43:17
|
thanks, for the update about the documentation. my application is now working behind esigate. But I do not like the links, that are generated. if am at the location http://localhost:8082/path/to/resource and my application is generating relative links "../../link/another/resource" then I am having this link in my html source "/path/to/resource/../../link/another/resource" is there a way to just get the link "/link/another/resource"? I tried using "esigate.fixMode=absolute", but then I am getting totally syntactically incorrect and therefore not working links. so my question is, is there a configuration option to just get "/link/another/resource" instead of "/path/to/resource/../../link/another/resource" in the html that esigate generates/changes? 2014-10-26 22:19 GMT+01:00 alexis thaveau <ale...@gm...>: > Hi, > > The documentation has been updated on 5.0-SNAPSHOT version ( > http://www.esigate.org/5.0-SNAPSHOT ) > > > > 2014-10-24 16:33 GMT+02:00 Volker Kümmer <vol...@gm...>: > > just want to let you know, that with the esigate server my wicket > > application is working (just one problem, that should be possible to > solve). > > So it seems that the proxyservlet is doing something different, as with > the > > filter my application is not working. > > > > just 2 little notes: > > - it would be helpful to correct the quickstart > > (http://www.esigate.org/quickstart.html) and add there the "s" to the > > mapping configuration, too > > - its just cosmetic, but it would be nice, if the description line for > 302 > > would be "Found", not "Temporary redirect" > > > > thanks for the help and pointers I've gotten here! > > > > 2014-10-24 14:16 GMT+02:00 Francois-Xavier Bonnet > > <fra...@ce...>: > >> > >> Can you try with "esigate.mappings" (with a "s")? > >> > >> 24 окт. 2014 г. 12:55 пользователь "Volker Kümmer" > >> <vol...@gm...> написал: > >>> > >>> >you should try esigate as a standalone proxy (esigate-server or > >>> > esigate-war). > >>> > >>> unfortunately I am not able to get esigate server working. It seems to > be > >>> any easy installation, but if I use this configuration > >>> > >>> esigate.remoteUrlBase=http://localhost:8080/ > >>> esigate.mapping=/* > >>> > >>> and this command for starting > >>> > >>> java -Desigate.config=esigate.properties -Dserver.port=8082 -jar > >>> esigate-server-5.0-SNAPSHOT.jar start > >>> > >>> I only get "No mapping defined for this url." when calling > >>> http://localhost:8082/ > >>> > >>> Am I doing something wrong? > >>> > >>> 2014-10-16 9:08 GMT+02:00 Nicolas Richeton <nic...@gm... > >: > >>>> > >>>> Hi Volker, > >>>> > >>>> The proxy filter is a new addition to esigate 5.0. > >>>> Your feedback is really valuable to catch the last bugs before the > >>>> stable release, but if you want something that just work, you should > try > >>>> esigate as a standalone proxy (esigate-server or esigate-war). > >>>> > >>>> We have several applications using esigate + wicket in production with > >>>> no issue. > >>>> > >>>> -- > >>>> Nicolas > >>>> > >>>> Le 15 oct. 2014 à 18:02, Volker Kümmer <vol...@gm...> a > >>>> écrit : > >>>> > >>>> hi > >>>> > >>>> good to know, that it should work in principle. > >>>> > >>>> I had not enough time, to really debug the problems, to see where it > >>>> originated from. > >>>> > >>>> But in the moment I am having two problems. > >>>> > >>>> 1. when the proxy filter is not in front of the wicket application, > if I > >>>> send a redirect after a post, I get es 302 redirect. But when the > ESIGate > >>>> proxy filter is in front of the application I will get an 307 > redirect -- I > >>>> do not know why in the moment. > >>>> > >>>> 2. when using the wicket ajax mechanisms I will always get an error -- > >>>> it works without any problems without the proxy filter: > >>>> > >>>> java.lang.IllegalStateException: WRITER > >>>> at org.mortbay.jetty.Response.getOutputStream(Response.java:564) > >>>> at > >>>> > org.esigate.servlet.impl.ResponseSender.sendResponse(ResponseSender.java:88) > >>>> at org.esigate.servlet.ProxyFilter.doFilter(ProxyFilter.java:67) > >>>> at > >>>> > org.mortbay.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1089) > >>>> at > >>>> > org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:365) > >>>> at > >>>> > org.mortbay.jetty.security.SecurityHandler.handle(SecurityHandler.java:216) > >>>> at > >>>> > org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181) > >>>> at > >>>> > org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712) > >>>> at > org.mortbay.jetty.webapp.WebAppContext.handle(WebAppContext.java:405) > >>>> at > >>>> > org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139) > >>>> at org.mortbay.jetty.Server.handle(Server.java:295) > >>>> at > >>>> > org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:503) > >>>> at > >>>> > org.mortbay.jetty.HttpConnection$RequestHandler.content(HttpConnection.java:841) > >>>> at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:639) > >>>> at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:210) > >>>> at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:379) > >>>> at > >>>> > org.mortbay.io.nio.SelectChannelEndPoint.run(SelectChannelEndPoint.java:361) > >>>> at > >>>> > org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442) > >>>> > >>>> > >>>> I am not using any esi or caching functionality. I have just > configured > >>>> the proxyfilter before the application. I will see, if I can get some > more > >>>> detailed information. > >>>> > >>>> > >>>> > >>>> 2014-10-15 9:24 GMT+02:00 Francois-Xavier Bonnet > >>>> <fra...@ce...>: > >>>>> > >>>>> Hi Volker, > >>>>> > >>>>> The beta-1 versions is currently being tested on a few projects. > Since > >>>>> this version, we have made a few improvements or bug fixes but no > blocking > >>>>> issue. > >>>>> Usually we release a new beta version every time we find a blocking > >>>>> issue that need a fix and the stable release comes when a major > project > >>>>> using EsiGate is ready to go to production. > >>>>> > >>>>> I would be very interested in having more information about the > errors > >>>>> you have. If a beta-2 is required, we could release it very quickly. > >>>>> > >>>>> 2014-10-13 17:35 GMT+02:00 Volker Kümmer <vol...@gm...>: > >>>>>> > >>>>>> Hello > >>>>>> > >>>>>> I would like to know, what the current state of ESIGate is? > >>>>>> > >>>>>> I was able (with the help of Francois-Xavier Bonnet -- thanks!) to > get > >>>>>> ESIGate configured, so that it served some content. > >>>>>> > >>>>>> But now I get some errors. I have ESIGate in front of a wicket > >>>>>> application and there are some problems with it. So I would like to > know, > >>>>>> whether there are some speciel configurations neccessary to get it > working > >>>>>> or if the beta-1 from february 2014 is simply outdated, > >>>>>> > >>>>>> In the moment my application runs behind ESIGate, but I have not set > >>>>>> any caching headers up to now. So I expected that the application > would work > >>>>>> as without ESIGate. > >>>>>> > >>>>>> If it should work with the beta-1 I will further investigate the > >>>>>> problem. But in the moment I just would like to know, if (these) > problems > >>>>>> are to be expected, as it is still a beta. > >>>>>> > >>>>>> kind regards > >>>>>> Volker > >>>>>> > >>>>>> > >>>>>> > ------------------------------------------------------------------------------ > >>>>>> Meet PCI DSS 3.0 Compliance Requirements with EventLog Analyzer > >>>>>> Achieve PCI DSS 3.0 Compliant Status with Out-of-the-box PCI DSS > >>>>>> Reports > >>>>>> Are you Audit-Ready for PCI DSS 3.0 Compliance? Download White paper > >>>>>> Comply to PCI DSS 3.0 Requirement 10 and 11.5 with EventLog Analyzer > >>>>>> http://p.sf.net/sfu/Zoho > >>>>>> _______________________________________________ > >>>>>> Webassembletool-users mailing list > >>>>>> Web...@li... > >>>>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >>>>>> > >>>>> > >>>> > >>>> > >>>> > ------------------------------------------------------------------------------ > >>>> Comprehensive Server Monitoring with Site24x7. > >>>> Monitor 10 servers for $9/Month. > >>>> Get alerted through email, SMS, voice calls or mobile push > >>>> notifications. > >>>> Take corrective actions from your mobile device. > >>>> http://p.sf.net/sfu/Zoho > >>>> > >>>> _______________________________________________ > >>>> Webassembletool-users mailing list > >>>> Web...@li... > >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >>> > >>> > >>> > >>> > >>> > ------------------------------------------------------------------------------ > >>> > >>> _______________________________________________ > >>> Webassembletool-users mailing list > >>> Web...@li... > >>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users > >>> > > > > > > > ------------------------------------------------------------------------------ > > > > _______________________________________________ > > Webassembletool-users mailing list > > Web...@li... > > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > > > |
|
From: alexis t. <ale...@gm...> - 2014-10-28 17:24:28
|
Bonsoir, Est-ce que vous pouvez fournir la configuration esigate (esigate.properties + web.xml) ? Pouvez vous aussi fournir le fichier de log (avec un niveau debug sur esigate ) ? Merci Le 28 octobre 2014 17:01, William Dupuis <wil...@gm...> a écrit : > Bonjour, > > Je vous contacte car j'ai un problème de redirection après une > authentification ProxyCAS dans ESIGate. > > > Détail de mon problème : > > J'ai installé un serveur ESIGate 5.0 en frontal de mes applications. Ce > serveur est cassifié et est utilisé comme ProxyCAS. > > Lorsque je teste le ProxyCAS sur les webapps de demo > (esigate-app-casified-aggregated1 et esigate-app-casified-aggregated2), cela > fonctionne bien. > Mes 2 webapps sont déployées dans le même Tomcat qu'ESIGate. > > Par contre, lorsque j'essaye d'inclure des applications tierces, je me > retrouve redirigé vers les applications tierces une fois connecté. > Pourtant en regardant les logs, l'authentification via ProxyCAS dans mes > applications tierces a bien fonctionné. > > Configuration du provider : > > appli.remoteUrlBase=http://adresse-locale:8080/appli/ > appli.extensions=org.esigate.servlet.ServletExtension,org.esigate.extension.Esi,org.esigate.cas.CasAuthenticationHandler > appli.mappings=/private/appli/* > > Scénario : > > J'accède à mon adresse ESIGate sécurisée : > http://adresse-esigate/esigate/private/appli/ > > Je suis redirigé vers mon CAS : > https://adresse-cas/cas/login?service=http%3A%2F%2Fadresse-esigate%2Fesigate%2Fprivate%2Fappli%2F > > Une fois authentifié dans CAS, je suis bien redirigé vers > http://adresse-esigate/esigate/private/appli/, puis je suis directement > redirigé avec une HTTP 302 vers mon adresse locale > http://adresse-locale:8080/appli/ > > Si je re-accède à mon URL ESIGate > (http://adresse-esigate/esigate/private/appli), cela fonctionne bien, je > suis authentifié. > > > Quelqu'un a-t-il déjà rencontré ce problème ? > Je n'arrive pas à déterminer si mon problème vient de ma configuration > ESIGate ou de mes applications tierces. > > > Merci d'avance pour votre retour. > Cordialement, > William Dupuis > > ------------------------------------------------------------------------------ > > _______________________________________________ > Webassembletool-users mailing list > Web...@li... > https://lists.sourceforge.net/lists/listinfo/webassembletool-users > |
|
From: William D. <wil...@gm...> - 2014-10-28 16:01:32
|
Bonjour, Je vous contacte car j'ai un problème de redirection après une authentification ProxyCAS dans ESIGate. *Détail de mon problème :* J'ai installé un serveur ESIGate 5.0 en frontal de mes applications. Ce serveur est cassifié et est utilisé comme ProxyCAS. Lorsque je teste le ProxyCAS sur les webapps de demo (esigate-app-casified-aggregated1 et esigate-app-casified-aggregated2), cela fonctionne bien. Mes 2 webapps sont déployées dans le même Tomcat qu'ESIGate. Par contre, lorsque j'essaye d'inclure des applications tierces, je me retrouve redirigé vers les applications tierces une fois connecté. Pourtant en regardant les logs, l'authentification via ProxyCAS dans mes applications tierces a bien fonctionné. *Configuration du provider :* appli.remoteUrlBase=http://adresse-locale:8080/appli/ appli.extensions=org.esigate.servlet.ServletExtension,org.esigate.extension.Esi,org.esigate.cas.CasAuthenticationHandler appli.mappings=/private/appli/* *Scénario :* J'accède à mon adresse ESIGate sécurisée : http://adresse-esigate/esigate/private/appli/ Je suis redirigé vers mon CAS : https://adresse-cas/cas/login?service=http%3A%2F%2Fadresse-esigate%2Fesigate%2Fprivate%2Fappli%2F Une fois authentifié dans CAS, je suis bien redirigé vers http://adresse-esigate/esigate/private/appli/, puis je suis directement redirigé avec une HTTP 302 vers mon adresse locale http://adresse-locale:8080/appli/ Si je re-accède à mon URL ESIGate ( http://adresse-esigate/esigate/private/appli), cela fonctionne bien, je suis authentifié. Quelqu'un a-t-il déjà rencontré ce problème ? Je n'arrive pas à déterminer si mon problème vient de ma configuration ESIGate ou de mes applications tierces. Merci d'avance pour votre retour. Cordialement, William Dupuis |
|
From: Romain <as...@gm...> - 2014-10-28 11:23:52
|
Je t'ai passé admin sur l'équipe Liferay de Smile-SA. Tu peux faire le changement de propriété. __ Romain Le 28 oct. 2014 à 11:20, alexis thaveau <ale...@gm...> a écrit : > Bonjour, > > Je viens de placer le code du prototype sur github > https://github.com/alexist/esigate-portlet > > > La portlet permet d'intégrer un block par provider, et ne gère pas > l'authentification. Vous trouverez un peu de doc sur le README du > projet > > N'hésitez pas à me contacter si vous rencontrez des problèmes. > > > > Le 23 octobre 2014 11:44, Ahmed Drira <ahm...@gm...> a écrit : >> Bonjour >> Merci Romain , j'ai déjà consulter les deux articles et c'est pour ça que >> j'ai choisie esigate ; >> >> @philippe est ce que je peut bénéficier de votre retour d'expérience avec ce >> POC >> >> >> Le 23 octobre 2014 10:19, Philippe De Oliveira >> <phi...@gm...> a écrit : >> >>> Bonjour, >>> >>> Oui c'est possible, j'ai fais un PoC exactement comme ça il y a moins d'un >>> an et ça fonctionne. >>> >>> Cordialement, >>> >>> 2014-10-22 22:00 GMT+02:00 Ahmed Drira <ahm...@gm...>: >>>> >>>> Bonjour >>>> est ce que possible de faire appel à esigate + esi:include pour intégrer >>>> une application tiers dans ma portail à travers une portlet >>>> bien sûre après avoir ajouter le filtre dans le web.xml de mon portlet et >>>> ajouter esigate-core et esigate-servlet avec mes jar >>>> >>>> Bien cordialement >>>> -- >>>> Ahmed DRIRA >>>> Computer engineer >>>> S.A.R.L. Alpha Engineering - Tunisia >>>> Résidence El Habib, Bloc 3 - Bureaux 33 & 34 >>>> 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis >>>> | URL : www.alpha-engineering.net >>>> | Mob : 55 61 47 88 >>>> | Te : 71 96 49 06 >>>> | Fax : 71 96 41 53 >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> >>>> _______________________________________________ >>>> Webassembletool-users mailing list >>>> Web...@li... >>>> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >>>> >>> >>> >>> >>> -- >>> Philippe De Oliveira >>> >> >> >> >> -- >> Ahmed DRIRA >> Computer engineer >> S.A.R.L. Alpha Engineering - Tunisia >> Résidence El Habib, Bloc 3 - Bureaux 33 & 34 >> 2, Rue du lac d'Annecy, Les Berges du Lac 1053 Tunis >> | URL : www.alpha-engineering.net >> | Mob : 55 61 47 88 >> | Te : 71 96 49 06 >> | Fax : 71 96 41 53 >> >> ------------------------------------------------------------------------------ >> >> _______________________________________________ >> Webassembletool-users mailing list >> Web...@li... >> https://lists.sourceforge.net/lists/listinfo/webassembletool-users >> |
5 messages has been excluded from this view by a project administrator.
