Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/23
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/24
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/commit/548d60449a40248e9b7fb2a8103a5e4419d6c290#commitcomment-14730299
The patch is unnecessary. The Tribes StringManager does not have to support
multiple locales whereas the main StringManager
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/25
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/115
Thanks for the PR. We have fixed this but with a simpler approach that
makes use of `ConcurrentDateFormat.formatRfc1123
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/115
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/118
Thanks for this. Working through a review of the patch now.
Note that there are some files that we can't change such as the Oracle
provided
Github user markt-asf commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/118#discussion_r209290720
--- Diff: java/org/apache/tomcat/dbcp/dbcp2/managed/ManagedConnection.java
---
@@ -1,4 +1,4 @@
-/**
+vi /**
--- End diff --
No
Github user markt-asf commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/118#discussion_r209292288
--- Diff: java/org/apache/catalina/ha/session/SessionMessageImpl.java ---
@@ -144,7 +144,7 @@ public String getEventTypeString()
case
Github user markt-asf commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/117#discussion_r209306777
--- Diff: webapps/docs/introduction.xml ---
@@ -89,6 +80,122 @@ same as $CATALINA_HOME.
+
+ Throughout the documentation, there
Github user markt-asf commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/117#discussion_r209308073
--- Diff: webapps/docs/introduction.xml ---
@@ -89,6 +80,122 @@ same as $CATALINA_HOME.
+
+ Throughout the documentation, there
Github user markt-asf commented on a diff in the pull request:
https://github.com/apache/tomcat/pull/117#discussion_r20982
--- Diff: webapps/docs/introduction.xml ---
@@ -89,6 +80,122 @@ same as $CATALINA_HOME.
+
+ Throughout the documentation, there
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/117
Looks great. Applied. Many thanks.
(note: there was one s/HOME/BASE/ required in the webapps section)
---
-
To unsubscribe
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/120
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/120
The double = is deliberate. The OP needs to RTFM.
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/122
Closing the PR as the requested change is not correct.
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/122
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/122
There is nothing in the spec that says Tomcat is required to do that.
---
-
To unsubscribe, e-mail: dev-unsubscr
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/30
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/33
Rename the page. If someone complains, we can look at adding a redirect
although we'll need to handle both Tomcat (for releases) and httpd (for the
website). I'd prefer to have a singl
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/33
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/47
Patch applied. Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/47
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/commit/d46012cb159c3384303eeceffc54eb78e6a62671#commitcomment-21553794
In java/org/apache/el/Messages.properties:
In java/org/apache/el/Messages.properties on line 32:
Let me take a closer
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/50
This change was made to trunk over 6 months ago.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/50
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/52
Spam
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/52
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/53
Spam
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/53
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/26
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/26#issuecomment-172488725
It appears this pull request was opened in error.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/27
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/27#issuecomment-184110339
Spam. This idiot has been blocked.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/28#issuecomment-188460191
Generally I like this patch. I do have a couple of comments:
- I think it makes sense to make the change to a generic approach
immediately. One way of doing this
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/124
Nice catch with handling the port. The patch I had come up with missed that.
I refactored populateHost() as it bugged me to set the server name one way
(that might throw an IOE and break the
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/125
I've skimmed this and it looks good. I'm currently buried in TLS 1.3 stuff
but wanted to let you know that the PR had been seen and that I hope to get it
into the next 9.0
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/126
-1 here too for much the same reason. A filter would work better for this.
Ignoring the thread related concerns, I'd also point out that new features
without a description of the use ca
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/126
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/127
Nice idea. I've applied a variation of this patch to Tomcat. The key
changes were:
- Only ignore source on Context elements
- Ignore source on Context elements in server.xml and contex
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/123
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/123
Thanks for reviewing this code and providing a patch. Unfortunately, we
plan to shortly move away from our custom signing service and switch to the
solution provided by DigiCert that integrates a
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/125
I've now spent some time looking at this more closely.
I like the idea of setting this once on the `Server` and then
auto-magically setting this on the `Connector`s.
As I rev
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/129
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/129
Thanks. Patch applied to 9.0.x, 8.5.x and 7.0.x for the next release of
each.
---
-
To unsubscribe, e-mail: dev-unsubscr
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/125
Patch has been applied with a few changes:
- portOffset was not cached on the Connector (to align with recent changes
to how port is handled)
- handle special case port values where the
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/130
I can see what you are trying to do but I'm not sure the change creates
enough of a visual separation to make much of a difference. I don't think it
will do much to reduce the
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/131
Spam. Reported to GitHub's abuse team.
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional com
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/131
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/132
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/132
Fixed in:
- trunk for 9.0.14 onwards
- 8.5.x for 8.5.36 onwards
- 7.0.x for 7.0.93 onwards
Thanks for the report and for the patch
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/134
How easy it is to get hold of the last modified date does vary by browser
but - given that Tomcat already provides this in the headers - I don't see much
benefit here. And micheal-o's
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/134
The browser history will give you what you need (to the minute anyway) in
both Chrome Firefox and IE. This is a generic solution that works for any web
page for any service - not just one page of
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/134
I tried adding a Last-Modified HTTP header but that didn't help. The
history approach looks to be the best solution at this
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/74
There is definitely some value here although we might not choose to skip
some parts of the patch. Let me pull in the obvious stuff and then we can see
what is left
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/74
I think I've pulled the obvious wins into Tomcat. Take a look and if you
think there is merit in further changes please feel free to open another pull
re
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/74
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/63
I've added some comments to the bugzilla issue on how this might be
addressed.
---
-
To unsubscribe, e-mail: dev-uns
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/73
Chris's original concern with the BZ 57767 patch (lack of Javadoc) still
needs to be addressed.
---
-
To unsubscribe, e
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/76
I did wonder if this would be better as configuration on WsFilter but on
reflection a separate Filter looks to be simpler for users to configure.
The patch needs documentation (webapps/docs
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/77
Making those classes final will cause problems if users have extended any
of them. While that seems unlikely, experience suggests it has probably been
done somewhere. Is there any reason
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/78
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/78
Thanks. Patch applied to trunk and back-ported to 8.5.x, 8.0.x and 7.0.x.
---
-
To unsubscribe, e-mail: dev-unsubscr
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/73
No objections to back-porting here.
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/79
Those aren't placeholders. It is intentional content. I believe they are
meant to be a lighthearted way of indicating that 'Context' is the only term
that ne
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/79
We could pull the entries and add "That's it!" after the list.
---
-
To unsubscribe, e-mail: dev-unsubscr...@to
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/83
The duplicated code is a sign that this could be handled elsewhere with
less code (i.e. in StringUtils)
---
-
To unsubscribe, e
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/82
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/83
Thanks for the proposed patch. I opted for a more general solution in
StringUtils since fixing that problem there should - in theory - prevent it
appearing anywhere else StringUtils is used
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/83
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/84
This needs a wider discussion on the dev list first.
However I do have some initial high level comments:
- The choice of package is unexpected
- Headers need to be standard ASF
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/76
Looking at this is on my TODO list to look at before the next release
---
-
To unsubscribe, e-mail: dev-unsubscr
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/73
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/85
Note there is a minor typo in the test method name. I'll fix that when I
apply the patch.
---
-
To unsubscribe, e-mail
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/87
Applied in r1815802
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/87
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/95
This is a partial fix. It only addresses the attributes of the mbean
element.
I'm wondering if, rather than duplicate the comments in the DTD file, if it
would be simpler to copy th
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/95
Thanks for the patch. There wasn't anything wrong with it but the more I
thought about it, the more I thought that referencing the DTD directly was a
better sol
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/95
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/96
The current OPTIONS behaviour is intentional.
OPTIONS lists the valid methods, not the permitted methods, for a resource.
The GET/POST issue is before my time with the project. There
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/96
The inconsistency stems from the different status codes used. If TRACE is
disabled at the connector, level then a 405 is returned for TRACE requests. If
readOnly is set in the DefaultServlet, a 403
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/96
I wanted to clear something up. It is not a case of me being willing to
change something or not. I don't get to decide these things on my own. It is a
community decision. Normally, we di
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/96
Getting back to whether readOnly should affect POST, my own view is that it
should not. readOnly refers to whether the default Servlet can change static
content. For static content request
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/96
Lack of response == lazy consensus. I plan to look at applying these
patches (or possibly a variation of them) before tagging 9.0.x
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/96
No argument with Konstantin's points here. I started to look at
implementing this and I realised that the WebDAV is inconsistent with how the
allow header is generated. A method may not be inc
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/96
I've fixed this in trunk. Given the behaviour changes (you can bet someone
depends on a 403 rather than a 405 response) I'm not going to back-port it.
The way I ended up tackling th
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/135
---
-
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/135
This has been fixed via
[POEditor](https://poeditor.com/projects/view?id=221603) and will be included
in 9.0.15 onwards
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/137
I'm all in favour of improving accessibility.
The changes to package.html and similar look good.
The changes to anything under test/ need to be reverted. Those are test
artefacts.
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/137
> Anyway, those package.html files are just fragments consumed by javadoc
tool. I suspect that changing the attributes of the HTML element does not have
any effect on generated Java
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/20#issuecomment-106360093
Starting Tomcat with an appBase that is not an existing directory is an
error and is reported as such in the logs.
---
If your project is set up for it, you can reply
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/21#issuecomment-109959429
OK. I've copied the Geronimo classes across and fixed the checkstyle and
compilation errors. I've now seen some additional issues that need to be
addres
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/21#issuecomment-110393102
1) I haven't reviewed the build.xml changes since I don't want to start
building this JAR until the API is correct.
2) Patch was incomplete. Applied
Github user markt-asf closed the pull request at:
https://github.com/apache/tomcat/pull/21
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/22#issuecomment-130565904
The patch appears to be quite large for a marginal benfit. Separating the
refactoring and the changes into separate commits would enable the true scale
of the changes
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/22#issuecomment-131576391
My comment regarding separating the refactoring and the functional changes
stands. It is not the refactoring I am against, it is the mixing of refactoring
and
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/19#issuecomment-87757450
-1.
Servlet 3.0 and later webapps have resource JARs (assuming the JAR is
packaged correctly). For single JAR apps, the Tomcat 8 resources implementation
can be
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/19#issuecomment-87983701
No. That is not what I am saying at all.
I am saying the functionality you state you want to add (serving JSPs from
within a JAR) can already be achieved by
Github user markt-asf commented on the pull request:
https://github.com/apache/tomcat/pull/15#issuecomment-69624704
This pull request is declined. Even ignoring the poor quality of this pull
request, supporting JSON formatted data is an application concern, not a
container concern
Github user markt-asf commented on the issue:
https://github.com/apache/tomcat/pull/58
Given the name of the method call, the proposed comment adds no value. The
patch also uses tabs rather than spaces.
---
If your project is set up for it, you can reply to this email and have your
1 - 100 of 133 matches
Mail list logo