-
-
Notifications
You must be signed in to change notification settings - Fork 131
Comments
Add support for sending events through proxy#397
Add support for sending events through proxy #397ndmanvar wants to merge 6 commits intogetsentry:master from
Conversation
lib/transports.js
Outdated
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will take care of this (for HTTPProxyTransport also)
@kamilogorek Can you please review and give me your thoughts/comments? (I know proxyAuth is still incomplete/TODO but wanted to get your thoughts/review on the rest of it)
ndmanvar
commented
Nov 17, 2017
Still need to write tests
33203dc to
954ee7a
Compare
For both HTTP and HTTPS endpoints. Uses tunnel-agent for https.
954ee7a to
6cce30b
Compare
21febae to
9a8a4c2
Compare
ndmanvar
commented
Jan 11, 2018
@kamilogorek can you please review when you get a chance? (:
kamilogorek
commented
Jan 12, 2018
@ndmanvar will do! I just wasn't sure if you're done with the tests :)
@kamilogorek
kamilogorek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks fine to me. Would you mind adding some docs to describe how to use proxies as well? :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You don't seem to use this object anywhere in tests
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
s/option/options/g
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about just using host port etc. instead? If we pass options object to this constructor, it's by definition mentioned to be used by proxy, therefore using a prefix proxyHost seems redundant.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Or it may be useful to distinguish http from httpProxy options. It's up to you really.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We could also check that it has been created correctly and assert on foo:123
kamilogorek
commented
Jan 16, 2018
@MaxBittker could you also take a peak at this code as well?
@MaxBittker
MaxBittker
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
hard to review some of the domain-specific logic, but if people are using some version of this successfully already that's a good signal! agree with kamil's comments, but i think this is looking good overall.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
slightly better comment here for what will happen if you send hostname or a link to a resource that justifies why?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
could this be commented to be more explanatory? not sure what these two branches mean
ghost
commented
May 28, 2018
Any updates on this? Would lodging a support request as a paying customer expedite this in anyway?
For both HTTP and HTTPS endpoints. Uses tunnel-agent for https.