grizzly handleEvent 在http server模块的使用场景

本文深入探讨了SSLFilter中的handleEvent方法实现及其应用场景。通过分析RequestUtils类中的证书填充逻辑及FilterChainContext的通知机制，揭示了SSLFilter如何在Grizzly框架中处理证书事件。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

一开始看到Filter中handleevent方法，debug设置断点却没有拦截到，第一感觉是很少使用到，但是看到SSLFilter却有handleevnent方法实现：

@Override public NextAction handleEvent(FilterChainContext ctx, FilterChainEvent event) throws IOException { if (event.type() == CertificateEvent.TYPE) { final CertificateEvent ce = (CertificateEvent) event; ce.certs = getPeerCertificateChain(getSSLEngine(ctx.getConnection()), ctx, ce.needClientAuth); return ctx.getStopAction(); } return ctx.getInvokeAction(); }

1.找到class org.glassfish.grizzly.http.server.util.RequestUtils 有使用到。

public static Object populateCertificateAttribute(final Request request) { Object certificates = null; if (request.getRequest().isSecure()) { SSLFilter.CertificateEvent event = new SSLFilter.CertificateEvent(true); try { request.getContext().notifyDownstream(event); } catch (IOException ioe) { if (LOGGER.isLoggable(Level.FINE)) { LOGGER.log(Level.FINE, ioe.toString(), ioe); } } certificates = event.getCertificates(); request.setAttribute(SSLSupport.CERTIFICATE_KEY, certificates); } return certificates; }

2.FilterChainContext：

public void notifyDownstream(final FilterChainEvent event) throws IOException { notifyDownstream(event, null); } public void notifyDownstream(final FilterChainEvent event, final CompletionHandler<FilterChainContext> completionHandler) throws IOException { final FilterChainContext newContext = getFilterChain().obtainFilterChainContext(getConnection()); newContext.setOperation(Operation.EVENT); newContext.event = event; newContext.setAddress(address); newContext.setStartIdx(filterIdx - 1); newContext.setFilterIdx(filterIdx - 1); newContext.setEndIdx(-1); newContext.customAttributes = getAttributes(); newContext.operationCompletionHandler = completionHandler; ProcessorExecutor.execute(newContext.internalContext); }

3.接下来和grizzly 执行filter一样，只不过调用filter的handleevent方法。