Recent searches
No recent searches

이은미(이지컴)
Joined Nov 29, 2022
·
Last activity Jul 17, 2024
Following
0
Followers
0
Total activity
31
Vote
1
Subscriptions
12
ACTIVITY OVERVIEW
BADGES
ARTICLES
POSTS
COMMUNITY COMMENTS
ARTICLE COMMENTS
ACTIVITY OVERVIEW
Latest activity by 이은미(이지컴)
이은미(이지컴) commented,
Hi Ryan,
Thanks for your suggestion.
I solved the problem by using a method of encoding only query parameters.
I was encoding the entire url.
View comment · Posted Mar 31, 2024 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments
이은미(이지컴) commented,
Hi Jingwei,
I couldn't solve it, so I just formatted my MacBook, and it worked out!
View comment · Posted Mar 31, 2024 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments
이은미(이지컴) created a post,
When I send the request using Postman or the fetch API, it works as expected and returns the desired response. However, with the ZAF client, I receive an error due to the '&' character in the URL.
I've tried using the encodeURIComponent()
function, but the issue persists.
I'm wondering if there is a specific configuration or option within the ZAF client that can handle this encoding issue. Any insights or suggestions would be greatly appreciated!
Posted Mar 21, 2024 · 이은미(이지컴)
0
Followers
4
Votes
1
Comment
이은미(이지컴) commented,
Fortunately, I found out the cause of the error.
I received mail from the company's developer yesterday.
He said,
As a result of checking about proxy server ip issue, it was a problem on our source
The cause was looking HTTP_X_FORWARDED_FOR value instead of the remote address.
I'm glad it worked out.
It wasn't a Zendesk issue, but thank you for helping me so far.
View comment · Posted Dec 27, 2023 · 이은미(이지컴)
0
Followers
1
Vote
0
Comments
이은미(이지컴) commented,
I'm sorry for the delay in answering.
Yes, it's already been added to the whitelist.
When I tested the proxy server, it was requested as `104.16.51.111/32` in the ingress list, but the actual firewall log showed a completely different `118.235.7.86`.
Even if the request is sent through Zendesk Proxy, do I still have to allow the End user Source IP to receive the Backed service ingress?
View comment · Posted Dec 22, 2023 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments
이은미(이지컴) commented,
I did what you told me to do, but there was an same error...
And I guess it was my mistake that zcli apps:create worked normally
View comment · Posted Dec 07, 2023 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments
이은미(이지컴) commented,
I don't run Linux when I'm using zcli, and my current default browser is chrome v.120.0.6099.62(latest version).
This error only appear when I run apps:validate, apps:package, apps:update, apps:create.
Only apps:new or apps:server command is working normally.
And when I run apps:package command, same error appears, but the weird thing is the zip file was made in the tmp folder. After I try to upload the created zip file directly from the admin center, it uploaded normally and work normally.
View comment · Edited Dec 07, 2023 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments
이은미(이지컴) commented,
I did an additional test yesterday, and I think the IPs that the host receiving are the IPs of ingress list, not on the egress list on the /ips.
But the company said that the firewall only allowed egress.
Is it correct that the proxy servers that the host should receive is ingress IP list?
View comment · Posted Dec 06, 2023 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments
이은미(이지컴) commented,
I'm using macOS Ventura 13.1 and node version is v21.2.0
View comment · Posted Dec 06, 2023 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments
이은미(이지컴) commented,
Sorry, I don't know the exact meaning of 'seeing IPs'.
I just know they allowed all the egress ips.
And when I asked to Zendesk Korea SC, he said, "I checked internally and found that the IP of the Zendesk Proxy server is included in '/ips', '216.198.0.0/18' ip range.".
Is there any way to allow Zendesk proxy server?
View comment · Edited Dec 05, 2023 · 이은미(이지컴)
0
Followers
0
Votes
0
Comments