Re: birthdate of AbstractHttp11Protocol.setRejectIllegalHeader
Wow. On https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html my chrome browser find of “AbstractHttp11Protocol" locates one instance down in 9.0.2. Find of setReject gets me zero hits?? None of the 17 hits for “deprecate", to my eye, pertain to changes in handling headers (I expected to locate a reference to the deprecation of AbstractHttp11Protocol.setRejectIllegalHeaderName). I’m very confused. For what it’s worth, I’m dealing with a misconfiguration in vaadin(v14) and spring-boot dependencies and I am trying to work out compatible versions of these. I’ve located the relevant releases of vaadin which break the spring dependencies and am heading over there now, so this Apache issue is of less importance to me. Thanks, rjs > On Jan 15, 2022, at 4:21 AM, Mark Thomas wrote: > > On 15/01/2022 02:42, Rob Sargent wrote: >> With version number as a surrogate date. I didn’t see any mention in the >> changelog. > > Look again. I see it in > > https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html > https://nightlies.apache.org/tomcat/tomcat-8.5.x/docs/changelog.html > > You won't see in 10.0.x or 10.1.x because the change occurred before the > branches were created. In those cases it is covered by the general entry for > the first version in the change log. > > Mark > > - > To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org > For additional commands, e-mail: users-h...@tomcat.apache.org > - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat GraalVm native image issue
On Sat, Jan 15, 2022 at 6:05 PM Satyajit Rout wrote: > > I want to serve the static file of a reactjs application through this > tomcat native image and I don't have any jar/war file to place under the > webapps folder. > > But tomcat native image is not running without a server.xml file in the > same path from where the native image is triggered. You have to place a server.xml and all the other usual configuration files in the conf folder, this is really the same thing as the usual Tomcat standalone. It seemed explicit enough when I wrote the sentence in the doc. The idea is to not duplicate the default server.xml (and all the others everywhere for no reason. Would you have understood it better if "The main configuration files are placed in the conf folder" -> "The usual configuration files for Tomcat standalone (server.xml, web.xml, etc) should be placed in the conf folder" ? Rémy > > Thanks, > Satyajit > > On Sat, 15 Jan 2022 at 22:29, Satyajit Rout > wrote: > > > > >> Hi Team, > >> > >> I am trying to build a native image of tomcat on GraalVM by referring to > >> the doc at > >> "https://tomcat.apache.org/tomcat-9.0-doc/graal.html#Building_the_native_image";. > >> > >> The documentation says, "Inside the tomcat-stuffed folder, the directory > >> structure is the same as for regular Tomcat. The main configuration files > >> are placed in the conf folder, and if using the default server.xml the > >> webapps are placed in the webapps folder." > >> > >> But if you clone the repo > >> "https://github.com/apache/tomcat/tree/main/modules/stuffed"; there is no > >> files inside tomcat/module/stuffed/conf folder except .gitignore file. > >> > >> After building the native image, while I am trying to run the native image > >> on another server it fails as it is *unable to find conf/server.xml on > >> that server*. Do we have any workaround to package the conf folder into > >> the native image or any other resolution for this issue? > >> > >> > >> Thanks & Regards, > >> > >> Satyajit > >> > >> - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
Re: Tomcat GraalVm native image issue
I want to serve the static file of a reactjs application through this tomcat native image and I don't have any jar/war file to place under the webapps folder. But tomcat native image is not running without a server.xml file in the same path from where the native image is triggered. Thanks, Satyajit On Sat, 15 Jan 2022 at 22:29, Satyajit Rout wrote: > >> Hi Team, >> >> I am trying to build a native image of tomcat on GraalVM by referring to the >> doc at >> "https://tomcat.apache.org/tomcat-9.0-doc/graal.html#Building_the_native_image";. >> >> The documentation says, "Inside the tomcat-stuffed folder, the directory >> structure is the same as for regular Tomcat. The main configuration files >> are placed in the conf folder, and if using the default server.xml the >> webapps are placed in the webapps folder." >> >> But if you clone the repo >> "https://github.com/apache/tomcat/tree/main/modules/stuffed"; there is no >> files inside tomcat/module/stuffed/conf folder except .gitignore file. >> >> After building the native image, while I am trying to run the native image >> on another server it fails as it is *unable to find conf/server.xml on that >> server*. Do we have any workaround to package the conf folder into the >> native image or any other resolution for this issue? >> >> >> Thanks & Regards, >> >> Satyajit >> >>
Re: Tomcat GraalVm native image issue
> > > Hi Team, > > I am trying to build a native image of tomcat on GraalVM by referring to the > doc at > "https://tomcat.apache.org/tomcat-9.0-doc/graal.html#Building_the_native_image";. > > The documentation says, "Inside the tomcat-stuffed folder, the directory > structure is the same as for regular Tomcat. The main configuration files are > placed in the conf folder, and if using the default server.xml the webapps > are placed in the webapps folder." > > But if you clone the repo > "https://github.com/apache/tomcat/tree/main/modules/stuffed"; there is no > files inside tomcat/module/stuffed/conf folder except .gitignore file. > > After building the native image, while I am trying to run the native image on > another server it fails as it is *unable to find conf/server.xml on that > server*. Do we have any workaround to package the conf folder into the native > image or any other resolution for this issue? > > > Thanks & Regards, > > Satyajit > >
Re: birthdate of AbstractHttp11Protocol.setRejectIllegalHeader
On 15/01/2022 02:42, Rob Sargent wrote: With version number as a surrogate date. I didn’t see any mention in the changelog. Look again. I see it in https://nightlies.apache.org/tomcat/tomcat-9.0.x/docs/changelog.html https://nightlies.apache.org/tomcat/tomcat-8.5.x/docs/changelog.html You won't see in 10.0.x or 10.1.x because the change occurred before the branches were created. In those cases it is covered by the general entry for the first version in the change log. Mark - To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
