In our setup we have a dispatcher instance in front of our author instance. We have a component with a mutifield and the author is allowed to fill in an external url if they want to. When they for example choose https://www.google.com:
![Screenshot 2020-04-01 at 13.15.15.png Screenshot 2020-04-01 at 13.15.15.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/23133i1665F70CF08842D4/image-size/large/is-moderation-mode/true?v=v2&px=999)
It returns a 403 error.
When we pass www.google.com it does work:
![Screenshot 2020-04-01 at 13.16.54.png Screenshot 2020-04-01 at 13.16.54.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/23134i01AA56B395FC1F12/image-size/large/is-moderation-mode/true?v=v2&px=999)
We have the following configuration set:
#Allow posts content, etc and servlets
/0007 { /type "allow" /glob "POST /content*"}
The weird thing is that this only happens when those values are stored within a multifield item, for example another component we have doesn't show this behavior. NOTE: in this component the data is not stored in a multifield item:
![Screenshot 2020-04-01 at 13.18.13.png Screenshot 2020-04-01 at 13.18.13.png](https://experienceleaguecommunities.adobe.com/t5/image/serverpage/image-id/23135iB91B74109CF379D5/image-size/large/is-moderation-mode/true?v=v2&px=999)
None of the 403 errors happen when we access the author instance directly, without a dispatcher in between.