[GitHub] [trafficserver] rob05c commented on pull request #9101: Fix handling of OPTIONS request

[GitBox <gi...@apache.org>]

rob05c commented on PR #9101:
URL: https://github.com/apache/trafficserver/pull/9101#issuecomment-1258776843

   Curious, what do you think about  https://datatracker.ietf.org/doc/html/rfc9112#section-3.2.4
   
   ```
   If a proxy receives an OPTIONS request with an absolute-form of
      request-target in which the URI has an empty path and no query
      component, then the last proxy on the request chain MUST send a
      request-target of "*" when it forwards the request to the indicated
      origin server.
   
      For example, the request
   
      OPTIONS http://www.example.org:8001/ HTTP/1.1
   
      would be forwarded by the final proxy as
   
      OPTIONS * HTTP/1.1
      Host: www.example.org:8001
   
      after connecting to port 8001 of host "www.example.org".
   ```
   
   ?
   
   It seems to me that we're violating the spec there. I think we're just not doing that replacement. And it's a `MUST`, so it's a strict spec violation.
   
   But how do we even know if we're the last proxy in the chain? Is there any way in the protocol or request or remap line to determine that? I'm not seeing one. Which means there's no way we can actually fulfill the spec? Unless we add some kind of remap or parent line or plugin or something to configure "remap is last proxy", that users would just have to manually set? Seems kind of terrible
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@trafficserver.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org