Re: [EsiGate-users] state of ESIGate

[Volker K. <vol...@gm...>]

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
> >
>