Hello Eric, Sorry for the late reply. The reason why you might be seeing DefaultDispatch in logs could be because other dispatches do not have logging statements in them and extend DefaultDispatch (e.g. URLDecodingDispatch).
This is weird,this should have fixed the issue. What do you see in the debug logs? debug logs should spit out the url Knox is dispatching request to. On Tue, Feb 23, 2021 at 11:13 AM Chufeng Gao <[email protected]> wrote: > Hello, > > > > I am a user of Knox 1.15.0. I tried to use it for the security of airflow > Web UI. However, I got kind of ‘double encoded’issue here. > > > > I got some encoded url pattern from Knox like this: > > ‘ > https://*.***.***.***:8443/gateway/sandbox/airflow/admin/airflow/trigger?dag_id=run_kaggle&origin=%252Fadmin%252Fairflow%252Ftree%253Fdag_id%253Drun_kaggle > ’. > > It seems the ‘/’in the parameters part has been encoded twice. > > > > Therefore, I added <dispatch > classname="org.apache.knox.gateway.dispatch.URLDecodingDispatch"/> in > service.xml to solve this problem. Then I cleaned all the stuff under > data/deployments and restarted the gateway. However, nothing changes. I > turned on the debug log and it seemed knox was still using DefaultDispatch. > > > > Also I had tried several other dispatches or tried to use configurable > dispatch. None of them worked. The debug log always showed that I > DefaultDispatch was used. > > > > I have been blocked by this issue for quite some time. Any help will be > appreciated! > > > > Sincerely, > > > > Eric Gao > > >
