Refactor use of `phantomjs_options` property

[ChrisBAshton]

There is an undocumented property as follows:

phantomjs_options: '--ssl-protocol=tlsv1'

This same option applies to CasperJS too. We should:

• rename the property, e.g. browser_engine_options
• add this property to the documentation and describe it properly
• (but we should also keep backwards compatibility for existing configs using phantomjs_options)

[spellfish]

This may be a silly question, but for the casperjs option is the property name "casperjs_options", or are phantomjs_options applied to both phantom and casper, assuming you're running both?

[ChrisBAshton]

No question is a silly question! Yes this property is passed to both engines. Which is why I've raised an issue to rename it (phantomjs_options is misleading).

[colorful-tones]

I've read through all threads related to this mysterious property: phantomjs_options: '--ssl-protocol=tlsv1'. Where does one use it, and how please? Does this get placed in the your config.yaml? And how does it work with CasperJS please?

[swati-qa]

Yes, this line needs to be added into your config.yaml file at the top, it resolves the issue where PhantomJS is been used (tried it myself). For CasperJS, I am myself trying to find that how does it helps there.