[CAUSEWAY-2454] CORS Filter not in FilterChain?

• Type: Bug
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.0.0-M4
• Fix Version/s: 2.0.0-M5
• Component/s: Viewer RO
• Environment: Windows 10

Docs Text

When I set a breakpoint at org.apache.shiro.web.servlet.AbstractShiroFilter:365 I see
chain.filters has 7++ non-null elements:

# characterEncodingFIlter
# webMvcMetricsFilter
# formContentFilter
# requestContextFilter
# ShiroFilter
# IsisLogOnExceptionFilter
# IsisRestfulObjectInteractionFilter
# Tomcat WebSocket (JSR356) Filter

but no CORS filter.

Is this as expected?

• Assignee: Jörg Rade
• Reporter: Jörg Rade
• Created: 26/Oct/20 13:31
• Updated: 01/Dec/21 17:21
• Resolved: 15/Nov/20 07:19

Description

Given: demo-wicket started from IntelliJ with Spring Boot Configuration, JDK11, Maven Goal 'Demo- Wicket: clean install'

When:  curl --user sven:pass -v -H "Access-Control-Request-Method: GET" -H "Origin: http://localhost:3000"   -X OPTIONS http://localhost:8080/restful/user

Actual: 

*   Trying 127.0.0.1...

• TCP_NODELAY set
• Connected to localhost (127.0.0.1) port 8080 (#0)
• Server auth using Basic with user 'sven'
  > OPTIONS /restful/user HTTP/1.1
  > Host: localhost:8080
  > Authorization: Basic c3ZlbjpwYXNz
  > User-Agent: curl/7.55.1
  > Accept: /
  > Access-Control-Request-Method: GET
  > Origin: http://localhost:3000
  >
  < HTTP/1.1 500
  < Set-Cookie: rememberMe=deleteMe; Path=/; Max-Age=0; Expires=Sun, 25-Oct-2020 10:13:42 GMT
  < Vary: Origin
  < Vary: Access-Control-Request-Method
  < Vary: Access-Control-Request-Headers
  < Access-Control-Allow-Origin: http://localhost:3000
  < Access-Control-Allow-Methods: GET
  < Access-Control-Allow-Credentials: true
  < Allow: GET, HEAD, POST, PUT, DELETE, TRACE, OPTIONS, PATCH
  < Content-Length: 0
  < Date: Mon, 26 Oct 2020 10:13:42 GMT
  < Connection: close
  <
• Closing connection 0

Expected: 

HTTP 200, Content-Length > 0

Issue Links

• relates to: CAUSEWAY-2768 [RO] Make Application Logo Available via REST