Greg Wilkins

Results 470 comments of Greg Wilkins

Containers should use the host header (or equivalent headers if Forwarded or X-forwarded support is configured) to determine the scheme, host and port to which are URL should be written.

@markt-asf The labels on this project are a bit of a mess and need a good cleanup. The projects are all EE related and while useful I'd also like to...

I think that in this regard the servlet spec is pretty clear. From [RequestDispatcher.forward](https://docs.oracle.com/javaee/7/api/javax/servlet/RequestDispatcher.html#forward-javax.servlet.ServletRequest-javax.servlet.ServletResponse-): > For a RequestDispatcher obtained via getRequestDispatcher(), the ServletRequest object has its path elements and parameters...

@arjantijms I'm really not keen on servlets having a CDI dependency. Surely it is whoever specifies `javax.enterprise.context.RequestScoped` annotation that should clarify this and provide any built-in default beans.

I think CDIs exact place/role in the EE ecosystem still needs to be resolved - and that wont happen within the servlet spec nor without architectural vision and guidance. If...

@arjantijms some EE projects re-basing on CDI while others wait for architectural vision/guidance is exactly what I mean by adhocery. I do think EE should indeed be based on DI...

I'm very cautious about going outside of the recommendation to limit header fields to US-ASCII. Allowing arbitrary bytes via arbitrary charset encodings is going to challenge containers to keep responses...

Note conversations regarding Jetty CDI integration with [OWB](https://issues.apache.org/jira/browse/OWB-1293) and [Weld](https://github.com/weld/core/pull/1926) indicating the need for an SPI.

See discussions: + https://download.oracle.com/javaee-archive/servlet-spec.java.net/jsr369-experts/2015/12/0318.html + https://www.eclipse.org/lists/servlet-dev/msg00103.html

Here are the proposals from the first thread: ```java /** * * This class represents a call-back mechanism that will notify implementations * as HTTP body parameters becomes available to...